See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/330872614

Requirement Analysis Document in Google Drive for Green and Sustainable

Software Engineering Approach

Article · November 2018

CITATIONS READS

0 304

4 authors, including:

Mohankumar Kumar Dr. M. Anand Kumar

Karpagam Academy of Higher Education Graphic Era University
32 PUBLICATIONS   64 CITATIONS    49 PUBLICATIONS   196 CITATIONS   

SEE PROFILE SEE PROFILE

Some of the authors of this publication are also working on these related projects:

Cloud Computing View project

Green and sustainable software engineering View project

All content following this page was uploaded by Mohankumar Kumar on 05 February 2019.

The user has requested enhancement of the downloaded file.

 International Journal of Recent Technology and Engineering (IJRTE)
ISSN: 2277-3878, Volume-7 Issue-4S, November 2018

Requirement Analysis Document in Google Drive

for Green and Sustainable Software Engineering
Approach
M. Mohankumar, M Anand Kumar, S. Aruna Devi, R. Suresh Kumar

Abstract: This study shows how a requirement analysis can In the modern requirements elicitation technique how it is
help to organizations become more environmentally sustainable helpful for green software system for reducing the
in a structured and efficient manner, for this we have analyzed environmental impacts during the requirement analysis or
the Google Drive document as a requirement analysis document
with the help of that document we try to cover the software
gathering the extent of requirement elicitation process.
requirement specification from the customer, then we try to Therefore we have two research questions
observe the if that document located in desktop pc what is the 1. How the modern technologies used for
cumulative processor energy, IA energy and GT energy, if that requirement engineering process?
document shared with cloud environment minimum and 2. If any one of the modern technologies reduces the
maximum communication of resource sharing details are processer power consumption while collecting the
analyzed for user base and data center of various regions, finally
the load event details are observed for the requirement document
requirement for software development process?
shared in the Google drive , This result show that the
technologies delivers specific suggestions for improvement both II. RELATED WORK
on reducing the environmental foot print of ICT and on using
ICT as a green solution for software requirement analysis A continuous research methodology are being proposed
process. from recent years to find the best suitable technique for
Keywords: Green ICT, IA Energy, GT Energy, Google Drive, observe the requirement analysis in green based software
Software Requirement Specification development life cycle approach ruzannachitchya et
al[1](sustainability design in RE)were among the first to
I. INTRODUCTION find out and suggested the sustainability education and
Requirement elicitation (RE) has much attention in rethink about professional norms and practices about
research and practice due to its importance to software software development life cycle phases, they also observer
project success. Requirements directly contribute to the individual findings about sustainability in requirement
appropriateness and cost effectiveness in the development of engineering process in professional environment and norms
a system. Where by RE is determinant of productivity and in professional practice, mendez Fernandez et.al[2]tried to
product quality. Improper RE makes the implementation of demonstrate practical difficulty related to Requirement
the entire requirement not feasible. Thus a proper decision engineering problems which constitutes a qualitative
has to be made on the Requirement engineering process for analysis of data that being obtained from 228 companies
the project to be successful. Requirement elicitation is the working out in ten different countries in various domain and
beginning stages in the software development life cycle. If reveal the problems faced by the practitioners they finding
the project failure is due to poor communication with more than ten problems that is related to requirement
analyst and user, so the objective of RE process is required engineering that is incomplete and /or hidden requirements,
to solve problems. Now days much technology has flaws in communication between requirement engineer and
introduced for Requirement Elicitation technique and customer, certain changes in business processes and goals,
provided with various possible technologies. So requirement un specified requirement, time boxing, misunderstanding
Engineering can use theseoptions for adopting green about the requirement project team, not giving proper
methodologies for developing software RE should focus on support by customer while gathering the requirement, and
green environment how to achieve this green environment weak access about customer requirement. Swati et al[3]
on earth. In the literature, found that the different elicitation recommended a software requirement prioritization
technique depends on time and resources and green software technique using fuzzy logic, they studied and finding out the
engineering. influence factors in requirement prioritization almost 14
technique and factors they stated like consistency,
traceability, priority basis etc. they created a framework
Revised Version Manuscript Received on 25 November, 2018. methodology in three phases that in training phase, fuzzy
Dr. M. Mohan Kumar, Assistant Professor Department of CS, IT and inference process, and testing phase and finally try to prove
CA, Karpagam Academy of Higher Education, Coimbatore (Tamil Nadu),
the predictable appropriate requirement prioritization
India.
Dr. M Anand Kumar, Professor, Adigrat University Ethiopia method. ummakhatuna[4] trying to declaring the green
Mrs. S. Aruna Devi, Assistant Professor, Department of Science and software engineering adaption in requirement elicitation
Humanities, Kumaraguru College of Technology, Coimbatore (Tamil process,
Nadu), India.
R. Suresh Kumar, Assistant Professor, Department of Electrical and
Electronics Engineering, Kumaraguru College of Technology, Coimbatore
(Tamil Nadu), India.

Published By:
Blue Eyes Intelligence Engineering
Retrieval Number: E1879017519 100 & Sciences Publication
 Requirement Analysis Document in Google Drive For Green And Sustainable Software Engineering Approach

tried to adopt the new green software systems using Damiano Torre[14]suggested the green and sustainable
existing technique and also demonstrate. Albert hankel [5] software engineering in higher education curriculum it was
highlight that ICT as a green solution for business processes, good idea to teach the student about green and sustainability
they further stated that participation of individuals like in early stages itself. Nasir Rashid[15] stated the risk factors
customer or requirement engineer awareness on what Green for vendors in green and sustainable software development
ICT can do improve the sustainability of a software method in agile technique in that they indentified the eight
engineering process in software development life cycle risk factors the very first risk factor was insufficient system
phases and also they identified the potential bottlenecks for documentation frequency range from 26 to 62 percentage.
further adoption about Green ICT. Erik jagroep[ 6]argue that Amit Mishra[16] stated the problems facing in requirement
rising energy consumption of ICT industry triggered for gathering , the problem due to communication gap between
more sustainability so they recommended the energy software developer and customer, some important
consumption based on software architecture. Paul [ 7] requirement missing because of the various software
suggest that the going green in ICT it will help to promote development process these factors affect the quality aspect
an eco-friendly and cleaner ecology it will also help to get of the software.Maqbool Ahmed Muhammad Azeem[17]
benefit like cost cutting, energy consumption and green stated that importance,the project requirement documents
house gases. They further says green computing is a great are the backbone of the project success and failures in that
development for future. Christophbecker ete [8]find out maqbool analysed the project success rate from 1994 to
software engineering practices for sustainability standard 2000 in that mainley identified factor was incomplete
current practice and focus of future practice in that they requirement details are 13.10%. resaon for project failure.
stated the requirement elicitation for current practice focus Hassan Reza[18]in that contribution of work describe the
on the features and immediate effects the stakeholders want design of requirement engineering tool it can be used to
in future the stakeholders understand the systems enabling speed up the requirement elicitiation and system
effects use creativity technique and long term scenarios to specification to improve the qualities in the areas of
forecast the potential structural impact then they says avilibaility, performance, and security based on quality
requirement validation key stakeholders verify that their attributes try to document the non functional requirements
interest are captured it ensure the understanding effects, in and quality aspect template. Huma Hayat Khan[19] describe
the requirement documentation task they find out the the global software development time how the requirement
current format of documentation not considering the engineering process influencing and creating a challenging
sustainability in future practice of requirement task like cultural and language differences,working
documentation template need to support analysts with check time,communication and coordination creating different
list.colin c. and Norbert seyff[9] also highlights the study challenges influencing the requirement engineering process
that explored the concept of sustainability requirement in and finally it concluded GSD based requirement engineering
order to understand how the term is being used in software process. Supavas Sitthithanasakul [20] tried to contribute the
and requirement engineering, in the design of study in new approch of software requiremnt engineering ontology
which they combines corpus linguistics and qualitative construction for the structured software requirement
content analysis. Finally the analysis shows the engineering process. These related work shows what happen
sustainability requirement may be considered as a red in requirement engineering process, it is because of there is
herring in the sense that it is constructed. Vivekshukla et el no user friendliness in maintain the document in both the
[10] tried to conduct a survey about requirement engineering customer and end user side so we tried the new approach
in that they find out different types of requirements they are with the help of Google drive document.
BRD that is business requirement documents, URD that is
User requirement document, SRD Software requirement III. RESEARCH METHODOLOGY
document it is further divided into two that is functional
The overarching research question guiding our analysis is
requirement and non functional requirements, they
the following how does current requirement technologies
specifically stated the software failure occur because of bad
playing a role in green sustainability in the software
requirement engineering.
requirement analysis. To answer it we conduct a analysis
Marimuthu and Chandrasekaran[12] tried to identify the
technique about green and sustainability with different
systematic mapping study for green and sustainable
software development teams. A selective set of questions
software engineering in that study they did software
that is related to green and sustainability aspect we raise this
engineering research topic classification in that software
questions to the various software development team and also
requirement and energy and sustainability related aspect
with the help of the modern technology we try to observe
topics was considered in 18 studies were published from
the energy consumption, CO2 emission , memory and CPU
2010 to may 2016.his research stated that more green and
utilization with the help of this factors we try to describe
sustainability related requirement analysis methodology
how the modern technology play a important role during
need to be done in future.komeilraisian[13] introduced a
software requirement analysis approach.(4
current challenges related to green and sustainable software
Ummakhantunajannat) find out three different classic
engineering he was created a conceptual model of the study
requirement elicitation process there are interviewing,
in that he was taken a SPLC(software product life
cycle)phases of development ,distribution ,usage ,disposal
and deactivation, in this conceptual model also not consider
the requirement analysis in green and sustainable aspect.

Published By:
Blue Eyes Intelligence Engineering
Retrieval Number: E1879017519 101 & Sciences Publication
 International Journal of Recent Technology and Engineering (IJRTE)
ISSN: 2277-3878, Volume-7 Issue-4S, November 2018

document anlaysis, interface analysis.

Interviewing: It’s a most common technique for
requirement analysis used by the software companies. This
process mostly based on question and answers with the help
of that question and answer try to discover the problem it
may be some time open discussion or direct meet with the
customer this classical methodology document mostly
maintain by paper base with different types of environment
some of the basic interview questions are mentioned in the
sustainability back ground check, sustainability related to
guideline in company [12].
Sustainability background check
1. Which of the following apply when it comes to
your Knowledge of sustainability?
a. You read about it in the news
b. You regularly have discussions with
friends/family/colleagues about it
c. You have read (at least one) book about it
d. You learn through active engagement in
community activities or political action Figure 2 describe the requirement representation details
e. You have a degree in a related discipline Based on this document the requirement engineer or
f. What else describes your knowledge and sources observer first have to type the requirement date, month and
of knowledge in sustainability? List anything that comes to year details, then they have to give the detail requirement
your mind. details for example if the requirement engineer type the
2. What do you do for sustainability in your daily following requirement information in the requirement
private life? Please list some concrete examples. details column the following figure 2 describe the
3. What do you do for sustainability in daily work requirement representation details
life? Please list some concrete examples The serial no 221 the details given by the requirement
4. What is your understanding of the term engineer about student community details grouping chart for
"sustainability"? Sustainability guidelines in place that the development team asking some clarification and
5. Are you aware of any standards/guidelines in your also they display the current grouping list in existing
company that relate to sustainability? (yes/no/I don't know). software package again the requirement engineer how the
If yes, which one(s) customer was expected in software like that he /she typed in
Requirement elicitation process for implementation: requirement analysis sheet that was maintained in Google
Here we maintain the Google drive document for drive doc. If they developer completed that process then
maintain the requirement and enhancement process of they give the process completion date after the buddy testing
software industries instead of paper baseFigure 1 shows the process that required changes released to the customer that
template format for requirement analysis process for one also mentioned in the released date column. This document
leading software company for educational software will helpful to software requirement observation this
development team and customer. document was shared with the both the development team
and requirement engineer and customer this type of
document will helpful to maintain the sustainability in
requirement elicitation process.
Method of Analysis:
Desktop
We try to analysis the requirement document in desktop
PC process with the help of tool Intel power gadget this tool
help to find out the RDTSC(Read Time- Stamp Counter)in
GhZ, Elapsed time in (seconds) CPU frequency, processor
power, cumulative processor energy in joules and
mWh(megawatt hour), IA power in Watt, Cumulative IA
energy in (joules) and energy in(mWh), package
temperature(cool and hot) GT(Generator Transformer)
Power in Watt, cumulative GT energy(joules)and(mWh)
these are all evaluated in CPU load and idle time and also
try to observe the memory utilization process the memory

Figure 1 shows the template format for requirement

analysis process for one leading software company for
educational software development team and customer.

Published By:
Blue Eyes Intelligence Engineering
Retrieval Number: E1879017519 102 & Sciences Publication
 Requirement Analysis Document in Google Drive For Green And Sustainable Software Engineering Approach

usage related to running the document. Table 1 Shows the servicing time also examine the data center loading, total
statistical information about document in the idle time and virtual machine cost and total data transfer cost are observed
processing time average power process details are with the help of clod analyst.
mentioned in Watt, total elapsed time(sec) and measured
Evaluation:
RDTSC frequency in (Ghz). It’s mostly in same in
requirement document process and idle and time. For example the requirement analysis document will be
shared to six regions that is Region zero north
Cloud analyst: America,Region one south America, region two---- region
This is the one of the approach if suppose if that three Asian countries region four African countries and
Requirement analysis document will maintained in the cloud region five Australia as shown in the figure , if we fix the
what is response time by various region, user base hourly document sharing simulation duration sixty minute for the
average response time in millisecond in the minimum and user bases from one to six user base for six region it shown
maximum details we will get, same way data center request in figure 3

Idle time process time

Parameters Ave. process power.
joules mWh joules mWh Ave. process power. Watt
Watt
Cumulative
1465.73 407.15 4.71 2064.96 573.6 6.61
processor Energy
Cumulative IA
380.39 105.66 1.22 946.14 262.82 3.03
Energy
Cumulative GT
53.68 14.91 0.17 65.49 18.19 0.21
Energy

Table 1 Shows the statistical information about document in the idle time and processing time average power process
details are mentioned in Watt, total elapsed time (sec) and measured RDTSC frequency.
If we run the simulation then it will show the following
details overall response time summary for the requirement
document sharing Table 2, Response time by region table 3,
Data center request servicing time in table 4.
Table 2 show the overall response time summary for the
requirement document sharing.
Details Avg (ms) Min (ms) Max (ms)
Overall response
50.11 37.61 61.06
time:
Data Center
0.49 0.02 0.9
processing time

70
Figure 3: Document sharing simulation duration sixty
minute for the user bases from one to six user base for 60
six region
50
40
Data Center
30 processing time

20 Overall
response time:
10
0
Avg (ms) Min Max
(ms) (ms)

Figure 5: Data Center Processing Time and Overall

Figure 4 shows the user base for each and every
Response Time in (ms)
regions was displayed that is(Data center) DC1 (User
Base)UB1 in region 0, DC2 UB2 for Region1, DC3 UB3
for Region2, DC4 UB4 for Region 3, and DC6 UB6 for
region 5.

Published By:
Blue Eyes Intelligence Engineering
Retrieval Number: E1879017519 103 & Sciences Publication
 International Journal of Recent Technology and Engineering (IJRTE)
ISSN: 2277-3878, Volume-7 Issue-4S, November 2018

User base Avg (ms) Min (ms) Max (ms)

1.6
UB1 50.19 37.61 60.86
1.4
UB2 49.99 38.64 60.40 1.2

UB3 49.95 38.88 61.06 1

Max (ms)
0.8
UB4 50.24 39.14 60.88 Min (ms)
0.6
UB5 50.16 37.66 60.66 Avg (ms)
0.4
UB6 50.11 38.86 60.61 0.2

Table 3 shows the Response time by region 0

DC1 DC2 DC3 DC4 DC5 DC6
70

60 Figure7: Data Center Request Details

So with the help of the cloud analysis tools the
50
requirement document sharing with various datacenter to
user base minimum, maximum and average request and
40 Avg (ms) response times we will get it will concluded that instead of
maintaining the requirement document in desktop pc if we
30 Min (ms)
maintain the document in cloud it will save the energy and
Max (ms) resource of the company. The figure 8 shows the simulation
20 result as follow as
10

0
UB1 UB2 UB3 UB4 UB5 UB6

Figure: 6 shows the user base Response time details

Data center Avg (ms) Min (ms) Max (ms)

DC1 0.46 0.02 0.86

DC2 0.50 0.03 0.89

DC3 0.49 0.02 0.88

DC4 0.50 0.02 0.88

DC5 0.50 0.03 0.90

Figure 8: Simulation Result

DC6 0.46 0.02 0.86
Google Drive document act as requirement document.
Suppose if the requirement analysis document sharing in
Table 4 shows the Data Center Request Servicing Time Google drive doc, the user could consider the three main
activities first one Google mail account opening time that is
page loading time of the Google mail account of the user,
second main activity google drive document page loading
time interval finally process was page loading time of the
requirement analysis document sharing the page load time.

Published By:
Blue Eyes Intelligence Engineering
Retrieval Number: E1879017519 104 & Sciences Publication
 Requirement Analysis Document in Google Drive For Green And Sustainable Software Engineering Approach

Event When How long Sum energy consumption also is very much reduced instead of
maintaining the document in desktop computer.
Redirect 0 0 0
IV. CONCLUSION
DNS 0 0 0
In this paper we proposed a requirement analysis
Connect 0 0 0 technique with the modern technology how it is differ from
Request 0 546 546 traditional approaches for example here we are using the of
Google drive document how to act as a requirement
Response 546 510 1056 engineering for observing the requirement of the end user
for the software company, here we also concluded that the
Dom 569 8124 9180
requirement document if we used in individual personal
Interactive 1632 0 - computer. The energy utilization in individual desktop pc
observed suppose if that document if we saved in cloud
Content Load 1632 0 - environment minimum and maximum response time of the
Load Event 8694 0 9180 various regions are analyzed , finally we concluded the
Google drive document in shared environment with the end
Table 5 shows the Google mail opening record details in user and development team, request and response load
8.6ms. event details are observed finally we concluded instead of
maintaining the requirement document in manual or desktop
Event When How long Sum Pc cloud based requirement analysis document approach
Redirect 0 446 446 was the best one compare to other approach it will save the
time and energy of individual and group of development
DNS 446 0 446 teams it also give the sustainable approach for software
development life cycle phases.
Connect 446 0 446
Request 626 323 769 REFERENCES
1. R. Chitchyan et al., "Sustainability Design in Requirements
Response 949 1668 2437 Engineering: State of Practice," 2016 IEEE/ACM 38th International
Conference on Software Engineering Companion (ICSE-C), Austin,
Dom 952 6096 8533 TX, 2016, pp. 533-542.
2. D. Mendez Fernandez, S. Wagner Naming the Pain in Requirements
Interactive 2713 0 - Engineering: Design of a Global Family of Surveys and First Results
from GermanyIn: Proc. of the 17th International Conference on
Content Load 2713 0 - Evaluation and Assessment in Software Engineering (EASE ’13),
ACM, 2013.
Load Event 7079 2 8535 3. S. Dhingra, Savithri G, M. Madan and Manjula R, "Selection of
prioritization technique for software requirement using Fuzzy Logic
Table 6 Google Drive Page Loading and Decision Tree," 2016 Online International Conference on Green
Engineering and Technologies (IC-GET), Coimbatore, 2016, pp. 1-
Event When How long Sum 11.
doi: 10.1109/GET.2016.7916822
4. UmmaKhatunaJannat ,‖ Green Software Engineering Adaption In
Redirect 0 0 0 Requirement Elicitation Process‖2016 international journal of
scientific & technology research volume 5, issue 08, august 2016 issn
DNS 0 0 0 2277-8616
5. A. Hankel and P. Lago, "How organisations can assess and improve
Connect 0 0 0 their green ICT activities in a standard and efficient way," 2016 ITU
Kaleidoscope: ICTs for a Sustainable World (ITU WT), Bangkok,
Request 28 6238 6238 2016, pp. 1-6
6. Erik Jagroep‖ Extending software architecture views with an energy
Response 6266 691 6929 consumption perspective Computing, 2017, Volume 99, Number 6,
Page 553
Dom 6271 5858 12787 7. Paul p.k,‖Is green computing a social software engineering
domain?‖,2016 international journal of applied science and
Interactive 9010 0 - engineering 4(2).PP.67-73
8. Becker, Colin (2016) Requirements: The Key to Sustainability. IEEE
Content Load 9010 0 - Software, 33 (1). pp. 56-65. ISSN 07407459
9. C. C. Venters et al., "Characterising Sustainability Requirements: A
Load Event 12129 0 12787 New Species Red Herring or Just an Odd Fish?," 2017 IEEE/ACM
39th International Conference on Software Engineering: Software
Engineering in Society Track (ICSE-SEIS), Buenos Aires, 2017, pp.
Table 7 Requirement Analysis Document Sharing the 3-12.
Page Load 10. VivekShukla, DhirendraPandey and Raj Shree. Article: Requirements
Engineering: A Survey. Communications on Applied
So it the above table record details shows the maximum Electronics3(5):28-31, November 2015. Published by Foundation of
of 12.1 ms is enough to share the requirement analysis Computer Science (FCS), NY, USA
document to team members of the development team and
also it will give the transparency in maintaining the
document in both the customer and development team

Published By:
Blue Eyes Intelligence Engineering
Retrieval Number: E1879017519 105 & Sciences Publication
 International Journal of Recent Technology and Engineering (IJRTE)
ISSN: 2277-3878, Volume-7 Issue-4S, November 2018

11. C. Becker, D. Walker and C. McCord, "Intertemporal Choice:

Decision Making and Time in Software Engineering," 2017
IEEE/ACM 10th International Workshop on Cooperative and Human
Aspects of Software Engineering (CHASE), Buenos Aires, 2017, pp.
23-29
12. C. Marimuthu K. Chandrasekaran," Software Engineering Aspects of
Green and Sustainable Software: A Systematic Mapping Study".
Proceedings of the 10th Innovations in Software Engineering
Conference Jaipur, India 2017 PP[ 34-44]
13. Komeilraisian,‖ Current Challenges And Conceptual Model of Green
And Sustainable Software Engineering,‖Journal of Theoretical and
Applied Information Technology
31st December 2016 -- Vol. 94. No. 2 – 2016
14. D. Torre, G. Procaccianti, D. Fucci, S. Lutovac and G. Scanniello,
"On the Presence of Green and Sustainable Software Engineering in
Higher Education Curricula," 2017 IEEE/ACM 1st International
Workshop on Software Engineering Curricula for Millennials
(SECM), Buenos Aires, 2017, pp. 54-60.
15. Rashid,‖ Developing Green and Sustainable Software Using Agile
Methods in Global Software Development: Risk Factors for
Vendors‖,2017 Proceedings of the 11th International Conference on
Evaluation of Novel Software Approaches to Software Engineering
ENASE 2016 PP 247—253
16. Maqbool Ahmed Muhammad Azeem,‖ Requirement Engineering the
backbone of a
project‖,2017,www.researchgate.net/publication/318787262,
17. H. Reza, R. Sehgal, J. Straub and N. Alexander, "Toward model-
based requirement engineering tool support," 2017 IEEE Aerospace
Conference, Big Sky, MT, 2017, pp. 1-10.
18. H. H. Khan, M. N. bin Mahrin and S. btChuprat, "Situational
requirement engineering framework for Global Software
Development," 2014 International Conference on Computer,
Communications, and Control Technology (I4CT), Langkawi, 2014,
pp. 224-229.
19. S. Sitthithanasakul and N. Choosri, "Application of software
requirement engineering for ontology construction," 2017
International Conference on Digital Arts, Media and Technology
(ICDAMT), Chiang Mai, 2017, pp. 447-453.
20. S.Arunadevi, Dr.VijetaIyer, ―A Study on M/M/C Queueing Model
under Monte Carlo Simulation in Traffic Model‖, 2017, International
Journal of pure and Applied Mathematics(IJPAM), No:12, vol 116,
pg:199-207.
21. http://sustainabilitydesign.org

Published By:
Blue Eyes Intelligence Engineering
Retrieval Number: E1879017519 106 & Sciences Publication
View publication stats