Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Case-study+submissions #67

Open
Erickprocopio opened this issue Nov 11, 2024 · 1 comment
Open

Case-study+submissions #67

Erickprocopio opened this issue Nov 11, 2024 · 1 comment

Comments

@Erickprocopio
Copy link

Case Study Template

*This is a template to use for case studies that are submitted to apply the SCI. *

Please delete the text in italics and replace it with the appropriate information.

For more information on any of the items, the final reference is the SCI Specification

If you find errors, or have further questions, please feel free to engage with us in the discussions section.

Overview

Please provide information describing the use case in a few bullet points

Architecture for the system under consideration

An architecture diagram of the system described in this use case

Technical details of the components in the architecture

Textual description with technical details of each component provided in the architecture diagram

Sites for Software Sustainability Actions

For each of the following sub-sections, indicate where and how actions can be taken in the following categories:

Energy Efficiency

  1. site of action
  2. description of the action

Hardware Efficiency

  1. site of action
  2. description of the action

Carbon Awareness

  1. site of action
  2. description of the action

Procedure

(What) Software boundary

Describe the components that are included in the software systems, if any major components are not included then please provide reasons for exclusion.

For example:

  • Front end mobile application
  • Network traffic between client mobile applications and servers
  • Network traffic between servers and database
  • Back-end servers.
  • Databases
  • Test infrastructure

(Scale) Functional unit

_Describe the functional unit that best controls the scaling of the software system.

The choice of functional unit applies to all components in your software boundary.

For example:

  • per API Call
  • per User
    _

(How) Quantification method

_For each software component in your software boundary, decide whether you are going to measure using real-world data or calculate an estimate via models, provide a reason and any useful details for each choice.

For example:

  • Front-end mobile application.

  • Calculate an estimate using a model that represents a single user using the application.

  • We do not have the right to export real-world measurements from individuals mobiles.

  • Back-end servers

  • Calculate an estimate of the energy consumption using models which take as input the CPU utilization of servers.

  • Calculate an estimate of the embodied carbon using the Treads low-resolution models based on AWS data.

Also, describe the reason for your choice

(Quantify) SCI Value Calculation

Show your work! For each of the component of your software system, show how you arrived at the SCI value.

Guidance for this is available in the Methodology summary section.

(Report)

Disclose the software boundary and your calculation methodology, including items that you might not have included in the previous sections

@Henry-WattTime
Copy link

Hello @Erickprocopio, did you mean to open this issue? Do you have a particular question or contribution? Or should we remove this issue? Thanks, Henry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants