New folderfac_lee023_HW06_WR5_FuncDecomp (3).pdfECE380 Pr.docxcurwenmichaela
New folder/fac_lee023_HW06_WR5_FuncDecomp (3).pdf
ECE380 Professional Seminar
Spring 2017
HW5 (WR5): Functional Decomposition
Date assigned: 3/13/17, Monday
Due date: Noon, 3/20/17, Monday
Max points: 20 pts.
Description:
Written Report 5 is on completing 3-level (i.e., Level 0, Level 1, and Level 2) functional
decomposition of your project. Each student shall individually submit one report that
shows complete functional decomposition of the project but also clearly identified
individual responsibilities for implementation. As such, all team members of a project
should first discuss and come up with a complete set of Level 1 subsystems that could be
implemented under balanced workloads among the team members. Then, each member
shall further elaborate his/her assigned Level 1 subsystems into Level 2.
This report should include block diagrams of all Level 0 ~ Level 2 subsystems and
corresponding tables of ALL subsystems with module name, inputs, outputs,
functionality (see pp. 93 ~ 98 of textbook by Ford and Coulston), AND responsible team
member.
Submission instructions:
Report length: No limit
How to submit: Upload onto EvalTools by the deadline shown above.
Grading:
Overall functional decomposition – team performance
Subsystems – individual performance
New folder/fac_lee023_HW11_WR6_FinalReport (1) (1).pdf
ECE380 Professional Seminar
Spring 2017
HW11: Final Report
Date assigned: 4/10/16, Monday
Due date: Noon, Monday, 4/24/17
Max points: 100 pts.
Description:
Each team’s final report must contain properly revised details of all project aspects covered
in this course, i.e., marketing and engineering requirements, proper description of the
project, 3-level functional decomposition, and project management including a well-
planned project plan presented in a Gantt chart.
To give incentive to a proper revision of functional decomposition, the final report will
carry 100 points of which 40 points will be allocated to the revised functional
decomposition (presented within the final report). Gantt chart (presented within the final
report) will have 10 points among the total of 100 points for the final report. The rest 50
points will go to the overall quality of the report as described in the review criteria.
Submission instructions:
Final Reports are team submissions so each document shall have all team member names
and only one person in the team shall upload the report to the designated submission link.
New folder/fac_lee023_HW11_WR6_FinalRpt_Guideline (1) (1).docxFinal Project Report Title ECE 380 Professional Seminar
by
Author(s) Name(s)
Author Affiliation(s)
E-mail
Date
Department of Electrical and Computer Engineering
Gannon University, Erie, PA
Acknowledgement
If you have any positive remarks this is the place to show your gratitude.
Abstract
The abstract is to be in fully-justified italicized text, as it is here, ...
New folderfac_lee023_HW06_WR5_FuncDecomp (3).pdfECE380 Pr.docxcurwenmichaela
New folder/fac_lee023_HW06_WR5_FuncDecomp (3).pdf
ECE380 Professional Seminar
Spring 2017
HW5 (WR5): Functional Decomposition
Date assigned: 3/13/17, Monday
Due date: Noon, 3/20/17, Monday
Max points: 20 pts.
Description:
Written Report 5 is on completing 3-level (i.e., Level 0, Level 1, and Level 2) functional
decomposition of your project. Each student shall individually submit one report that
shows complete functional decomposition of the project but also clearly identified
individual responsibilities for implementation. As such, all team members of a project
should first discuss and come up with a complete set of Level 1 subsystems that could be
implemented under balanced workloads among the team members. Then, each member
shall further elaborate his/her assigned Level 1 subsystems into Level 2.
This report should include block diagrams of all Level 0 ~ Level 2 subsystems and
corresponding tables of ALL subsystems with module name, inputs, outputs,
functionality (see pp. 93 ~ 98 of textbook by Ford and Coulston), AND responsible team
member.
Submission instructions:
Report length: No limit
How to submit: Upload onto EvalTools by the deadline shown above.
Grading:
Overall functional decomposition – team performance
Subsystems – individual performance
New folder/fac_lee023_HW11_WR6_FinalReport (1) (1).pdf
ECE380 Professional Seminar
Spring 2017
HW11: Final Report
Date assigned: 4/10/16, Monday
Due date: Noon, Monday, 4/24/17
Max points: 100 pts.
Description:
Each team’s final report must contain properly revised details of all project aspects covered
in this course, i.e., marketing and engineering requirements, proper description of the
project, 3-level functional decomposition, and project management including a well-
planned project plan presented in a Gantt chart.
To give incentive to a proper revision of functional decomposition, the final report will
carry 100 points of which 40 points will be allocated to the revised functional
decomposition (presented within the final report). Gantt chart (presented within the final
report) will have 10 points among the total of 100 points for the final report. The rest 50
points will go to the overall quality of the report as described in the review criteria.
Submission instructions:
Final Reports are team submissions so each document shall have all team member names
and only one person in the team shall upload the report to the designated submission link.
New folder/fac_lee023_HW11_WR6_FinalRpt_Guideline (1) (1).docxFinal Project Report Title ECE 380 Professional Seminar
by
Author(s) Name(s)
Author Affiliation(s)
E-mail
Date
Department of Electrical and Computer Engineering
Gannon University, Erie, PA
Acknowledgement
If you have any positive remarks this is the place to show your gratitude.
Abstract
The abstract is to be in fully-justified italicized text, as it is here, ...
Paper Title (use style paper title)Note Sub-titles are not.docxaman341480
Paper Title* (use style: paper title)
*Note: Sub-titles are not captured in Xplore and should not be used
line 1: 1st Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 4th Given Name Surname
line 2: dept. name of organization(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 2nd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 5th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 3rd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 6th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
Abstract—This electronic document is a “live” template and already defines the components of your paper [title, text, heads, etc.] in its style sheet. *CRITICAL: Do Not Use Symbols, Special Characters, Footnotes, or Math in Paper Title or Abstract. (Abstract)
Keywords—component, formatting, style, styling, insert (key words)
I. Introduction (Heading 1)
This template, modified in MS Word 2007 and saved as a “Word 97-2003 Document” for the PC, provides authors with most of the formatting specifications needed for preparing electronic versions of their papers. All standard paper components have been specified for three reasons: (1) ease of use when formatting individual papers, (2) automatic compliance to electronic requirements that facilitate the concurrent or later production of electronic products, and (3) conformity of style throughout a conference proceedings. Margins, column widths, line spacing, and type styles are built-in; examples of the type styles are provided throughout this document and are identified in italic type, within parentheses, following the example. Some components, such as multi-leveled equations, graphics, and tables are not prescribed, although the various table text styles are provided. The formatter will need to create these components, incorporating the applicable criteria that follow.
II. Ease of Use
A. Selecting a Template (Heading 2)
First, confirm that you have the correct template for your paper size. This template has been tailored for output on the A4 paper size. If you are using US letter-sized paper, please close this file and download the Microsoft Word, Letter file.
B. Maintaining the Integrity of the Specifications
The template is used to format your paper and style the text. All margins, column widths, line spaces, and text fonts are prescribed; please do n.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Paper Title (use style paper title)Note Sub-titles are not.docxaman341480
Paper Title* (use style: paper title)
*Note: Sub-titles are not captured in Xplore and should not be used
line 1: 1st Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 4th Given Name Surname
line 2: dept. name of organization(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 2nd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 5th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 3rd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 6th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
Abstract—This electronic document is a “live” template and already defines the components of your paper [title, text, heads, etc.] in its style sheet. *CRITICAL: Do Not Use Symbols, Special Characters, Footnotes, or Math in Paper Title or Abstract. (Abstract)
Keywords—component, formatting, style, styling, insert (key words)
I. Introduction (Heading 1)
This template, modified in MS Word 2007 and saved as a “Word 97-2003 Document” for the PC, provides authors with most of the formatting specifications needed for preparing electronic versions of their papers. All standard paper components have been specified for three reasons: (1) ease of use when formatting individual papers, (2) automatic compliance to electronic requirements that facilitate the concurrent or later production of electronic products, and (3) conformity of style throughout a conference proceedings. Margins, column widths, line spacing, and type styles are built-in; examples of the type styles are provided throughout this document and are identified in italic type, within parentheses, following the example. Some components, such as multi-leveled equations, graphics, and tables are not prescribed, although the various table text styles are provided. The formatter will need to create these components, incorporating the applicable criteria that follow.
II. Ease of Use
A. Selecting a Template (Heading 2)
First, confirm that you have the correct template for your paper size. This template has been tailored for output on the A4 paper size. If you are using US letter-sized paper, please close this file and download the Microsoft Word, Letter file.
B. Maintaining the Integrity of the Specifications
The template is used to format your paper and style the text. All margins, column widths, line spaces, and text fonts are prescribed; please do n.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
JMeter webinar - integration with InfluxDB and Grafana
Sbc template
1. Instructions for Authors of SBC Conferences
Papers and Abstracts
Luciana P. Nedel1, Rafael H. Bordini2, Flávio Rech Wagner1, Jomi F. Hübner3
1Instituto de Informática – Universidade Federal do Rio Grande do Sul (UFRGS)
Caixa Postal 15.064 – 91.501-970 – Porto Alegre – RS – Brazil
2Department of Computer Science – University of Durham
Durham, U.K.
3Departamento de Sistemas e Computação
Universidade Regional de Blumenau (FURB) – Blumenau, SC – Brazil
{nedel,flavio}@inf.ufrgs.br, R.Bordini@durham.ac.uk, jomi@inf.furb.br
Abstract. This meta-paper describes the style to be used in articles and short
papers for SBC conferences. For papers in English, you should add just an
abstract while for the papers in Portuguese, we also ask for an abstract in
Portuguese (“resumo”). In both cases, abstracts should not have more than
10 lines and must be in the first page of the paper.
Resumo. Este meta-artigo descreve o estilo a ser usado na confecção de
artigos e resumos de artigos para publicação nos anais das conferências
organizadas pela SBC. É solicitada a escrita de resumo e abstract apenas
para os artigos escritos em português. Artigos em inglês deverão apresentar
apenas abstract. Nos dois casos, o autor deve tomar cuidado para que o
resumo (e o abstract) não ultrapassem 10 linhas cada, sendo que ambos
devem estar na primeira página do artigo.
1. General Information
All full papers and posters (short papers) submitted to some SBC conference, including
any supporting documents, should be written in English or in Portuguese. The format
paper should be A4 with single column, 3.5 cm for upper margin, 2.5 cm for bottom
margin and 3.0 cm for lateral margins, without headers or footers. The main font must
be Times, 12 point nominal size, with 6 points of space before each paragraph. Page
numbers must be suppressed.
Full papers must respect the page limits defined by the conference. Conferences
that publish just abstracts ask for one-page texts.
2. First Page
The first page must display the paper title, the name and address of the authors, the
abstract in English and “resumo” in Portuguese (“resumos” are required only for papers
written in Portuguese). The title must be centered over the whole page, in 16 point
boldface font and with 12 points of space before itself. Author names must be centered
in 12 point font, bold, all of them disposed in the same line, separated by commas and
with 12 points of space after the title. Addresses must be centered in 12 point font, also
2. with 12 points of space after the authors’ names. E-mail addresses should be written
using font Courier New, 10 point nominal size, with 6 points of space before and 6
points of space after.
The abstract and “resumo” (if is the case) must be in 12 point Times font,
indented 0.8cm on both sides. The word Abstract and Resumo, should be written in
boldface and must precede the text.
3. CD-ROMs and Printed Proceedings
In some conferences, the papers are published on CD-ROM while only the abstract is
published in the printed Proceedings. In this case, authors are invited to prepare two
final versions of the paper. One, complete, to be published on the CD and the other,
containing only the first page, with abstract and “resumo” (for papers in Portuguese).
4. Sections and Paragraphs
Section titles must be in boldface, 13pt, flush left. There should be an extra 12 pt of
space before each title. Section numbering is optional. The first paragraph of each
section should not be indented, while the first lines of subsequent paragraphs should be
indented by 1.27 cm.
4.1. Subsections
The subsection titles must be in boldface, 12pt, flush left.
5. Figures and Captions
Figure and table captions should be centered if less than one line (Figure 1), otherwise
justified and indented by 0.8cm on both margins, as shown in Figure 2. The caption font
must be Helvetica, 10 point, boldface, with 6 points of space before and after each
caption.
Figure 1. A typical figure
3. Figure 2. This figure is an example of a figure caption taking more than one
line and justified considering margins mentioned in Section 5.
In tables, try to avoid the use of colored or shaded backgrounds, and avoid thick,
doubled, or unnecessary framing lines. When reporting empirical data, do not use more
decimal digits than warranted by their precision and reproducibility. Table caption must
be placed before the table (see Table 1) and the font used must also be Helvetica, 10
point, boldface, with 6 points of space before and after each caption.
Table 1. Variables to be considered on the evaluation of interaction techniques
6. Images
All images and illustrations should be in black-and-white, or gray tones, excepting for
the papers that will be electronically available (on CD-ROMs, internet, etc.). The image
resolution on paper should be about 600 dpi for black-and-white images, and 150-300
dpi for grayscale images. Do not include images with excessive resolution, as they may
take hours to print, without any visible difference in the result.
4. 7. References
Bibliographic references must be unambiguous and uniform. We recommend giving
the author names references in brackets, e.g. [Knuth 1984], [Boulic and Renault 1991];
or dates in parentheses, e.g. Knuth (1984), Smith and Jones (1999).
The references must be listed using 12 point font size, with 6 points of space
before each reference. The first line of each reference should not be indented, while the
subsequent should be indented by 0.5 cm.
References
Boulic, R. and Renault, O. (1991) “3D Hierarchies for Animation”, In: New Trends in
Animation and Visualization, Edited by Nadia Magnenat-Thalmann and Daniel
Thalmann, John Wiley & Sons ltd., England.
Dyer, S., Martin, J. and Zulauf, J. (1995) “Motion Capture White Paper”,
http://reality.sgi.com/employees/jam_sb/mocap/MoCapWP_v2.0.html, December.
Holton, M. and Alexander, S. (1995) “Soft Cellular Modeling: A Technique for the
Simulation of Non-rigid Materials”, Computer Graphics: Developments in Virtual
Environments, R. A. Earnshaw and J. A. Vince, England, Academic Press Ltd., p.
449-460.
Knuth, D. E. (1984), The TeXbook, Addison Wesley, 15th edition.
Smith, A. and Jones, B. (1999). On the complexity of computing. In Advances in
Computer Science, pages 555–566. Publishing Press.