software metrics and quality engineering ACCEPTABLE TYPES OF PROJECTS

Anonymous

Question Description

The details are given below.

Acceptable types of projects

The project will be of two generic types:
  • Application project: An application of a specific set of software metrics and/or quality engineering techniques discussed in class and a report of the activities, experience and related findings. For example, you may define/select/collect metrics data from one of your company's projects, perform various analyses, and identify problematic areas for focused quality/productivity improvement.
    It is a good idea to consider multiple metrics, preferably from different metrics categories. For example, some internal, some external metrics. When you measure quality, multiple quality attributes/characteristics are preferable to a single one. For this reason, and for a good learning experience, a pure SRE (software reliability engineering) project is not suitable for this class, although it might be perfectly OK for CSE 8317 Software Reliability and Safety, which covers a subset of the quality metrics we cover in this class, together with other material not covered here and in more depth.
  • Term research paper: A term paper covering some in-depth (theoretical or fundamental research) and/or up-to-date (research done in the last few years) study of a chosen topic. If you choose this option, you must study at least three papers (no survey papers as your sources, please!) of a closely related topic thoroughly, and your conclusions and observations must be your own based on your own experience, specifically conducted cases studies, and/or logical reasoning. The summary of the chosen papers is only a small part of your term paper, the focus should be on issues mentioned above. One concrete example is a study of hypothesis testing using metrics data. Another example is metrics usage and modeling for cloud computing as a new application area.
    (For those of you who are familiar with technical publications, your term research paper is similar to some "survey papers" you see from time to time in journals. --- You see, your are producing a survey paper here. That's why I don't want you to use survey papers as your primary sources.)
Students may form a team to do a application-type project if it is of a larger scale/scope that requires team effort (must be well justified). However, if one chooses to write a term paper, it should be an individual effort.

Project Proposal (and Pre-Proposal)

You project proposal should be around 3-5 double spaced pages in length, and should include the following information:
  • a proper title (not just project for CSE 8314)
  • an proper abstract, that should be written as an executive summary
  • clearly identify the problem that you are going to address, or topic area for your term paper,
  • some basic background information,
  • the solution strategy you intend to use (what are you going to measure? how? which analysis/modeling technique? etc.) for your application project or a selected topic areas with some candidate papers or sources.
  • a rough schedule
  • for application-type projects, you also need to discuss:
    • measurement implementation and data collection,
    • analysis of result to be performed,
    • followup actions,
  • for term papers, you also need to pay attention to:
    • importance and relevance of the selected topic and its relation to the specific topic(s) we discussed in class.
    • importance and contribution of candidate papers
    • diversity of candidate papers, all or most should be from diverse published sources (see my comments about hw#1).
    • if you have access to relevant internal reports, they will probably be more relevant, but you should tie them to the "state-of-art" published research.
In case of a group project (application project only, not term paper), please also provide information regarding roles and responsibilities.

Project presentation

Each presentation will be between 15 and 30 minutes. Please focus more on the important activities and findings, not too much on the background and details.

Project report

A project report or term paper should be around 15 double-spaced pages in length, and clearly and comprehensively describes the background, problem, strategy, metrics, activities, result analysis, lessons learned, followup actions, and summary/conclusions. A high level summary or an abstract should also be included at the beginning of your report.

If you'd like to, raw data and detailed modeling/analysis activities should be included in the appendix. Remember, it is a "report" after all. Not a collection of data and models without description/discussion.

For term papers, please also include, in the appendix, the titles and abstracts of the papers your covered in detail. In additional, if the paper(s) was not publicly available (e.g., internal reports), you need to include a copy of the paper(s) with your report. These documents are not counted in the 15-page limit.

Tutor Answer

Robert__F
School: UIUC

check and let me know to prepare the presentation

Running head: SOFTWARE METRICS FOR GREEN IT

1

Software metrics for Green IT

Contents
Introduction ......................................................................................................................... 2
Why look at software metrics ............................................Error! Bookmark not defined.
Tracking product lifecycle .................................................Error! Bookmark not defined.
Software for sustainability .................................................Error! Bookmark not defined.
Software efficiency and data processing ............................ Error! Bookmark not defined.
Cloud Computing ........................................................... Error! Bookmark not defined.
MIS Software .................................................................Error! Bookmark not defined.
Issues ..................................................................................Error! Bookmark not defined.
Conclusion .........................................................................Error! Bookmark not defined.
References ..........................................................................Error! Bookmark not defined.

SOFTWARE METRICS FOR GREEN IT
Introduction
Global warming has made it imperative for diverse industries to look at ways to reduce
energy consumption, while maintaining functionality. This can be measured through energy
efficiency. Within the IT industry, most methods to reduce energy consumption have been
focused on hardware. The attention has gone toward developing hardware and use methods that
will reduce energy consumption patterns. However, over the last few years, developers have
realized the scope for reducing energy consumption by creating green software. Few studies
however, have focused on how software can become more energy efficient. As a matter of fact,
there is no way to describe what constitutes energy efficient software. In this paper, there has
been an effort made to study software metrics for energy efficiency, and to look at the existing
challenges and possible solutions.

2


Running head: SOFTWARE METRICS FOR GREEN IT

Software metrics for Green IT
[Author Name(s), First M. Last, Omit Titles and Degrees]
[Institutional Affiliation(s)]

Author Note

1

SOFTWARE METRICS FOR GREEN IT

2

Contents
Introduction ......................................................................................................................... 3
Why look at software metrics ............................................................................................. 3
Tracking product lifecycle .................................................................................................. 4
Software for sustainability .................................................................................................. 6
Software efficiency and data processing ........................................................................... 10
Cloud Computing ...........................................................................................................11
MIS Software ................................................................................................................ 12
Issues ................................................................................................................................. 13
Conclusion ........................................................................................................................ 14
References ......................................................................................................................... 16

SOFTWARE METRICS FOR GREEN IT

3

Software metrics for Green IT
Introduction
Global warming has made it imperative for diverse industries to look at ways to reduce
energy consumption, while maintaining functionality. This can be measured through energy
efficiency. Within the IT industry, most methods to reduce energy consumption have been
focused on hardware. The attention has gone toward developing hardware and use methods that
will reduce energy consumption patterns. However, over the last few years, developers have
realized the scope for reducing energy consumption by creating green software. Few studies
however, have focused on how software can become more energy efficient. As a matter of fact,
there is no way to describe what constitutes energy efficient software. In this paper, there has
been an effort made to study software metrics for energy efficiency, and to look at the existing
challenges and possible solutions.
Why look at software metrics
Conventionally, software metrics have enabled developers to track aspects such as return
on investment, workload, overtime and costs. It has also helped developers compare the
software performance in terms of these metrics. This had led to the thrust toward further
improvements. Metrics have helped developers look at the efficiency of the work flow and fine
tune the process.
Software metrics tracking also helps managers, in addition to developers. It helps
managers look at the metrics for ways to enhance productivity. As developers and managers are
aware, problems located in the initial stages of the development process are easier to solve. Also,
the expense for resolving problems in the initial stages is low. (Stringfellow, 2017).

SOFTWARE METRICS FOR GREEN IT

4

Stringfellow (2017) offers some general criteria for determining software metrics. The metrics
should be easy to compute. They should be simple. They need to be free from ambiguity. One
metric should track one unit of measurement. The metrics need to be cost effective to obtain.
They should be valid and reliable. One aspect that the author mentions is adaptability. As we
look to adapt existing metrics to assess green friend...

flag Report DMCA
Review

Anonymous
Thanks, good work

Brown University





1271 Tutors

California Institute of Technology




2131 Tutors

Carnegie Mellon University




982 Tutors

Columbia University





1256 Tutors

Dartmouth University





2113 Tutors

Emory University





2279 Tutors

Harvard University





599 Tutors

Massachusetts Institute of Technology



2319 Tutors

New York University





1645 Tutors

Notre Dam University





1911 Tutors

Oklahoma University





2122 Tutors

Pennsylvania State University





932 Tutors

Princeton University





1211 Tutors

Stanford University





983 Tutors

University of California





1282 Tutors

Oxford University





123 Tutors

Yale University





2325 Tutors