| Methods' Summary |
| getPrintAreas |
returns a sequence containing all print areas of the sheet.
|
| setPrintAreas |
sets the print areas of the sheet.
|
| getPrintTitleColumns |
returns, whether the title columns are repeated on all subsequent
print pages to the right.
|
| setPrintTitleColumns |
specifies whether the title columns are repeated on all subsequent
print pages to the right.
|
| getTitleColumns |
returns the range that is specified as title columns range.
|
| setTitleColumns |
specifies a range of columns as title columns range.
|
| getPrintTitleRows |
returns, whether the title rows are repeated on all subsequent
print pages to the bottom.
|
| setPrintTitleRows |
specifies whether the title rows are repeated on all subsequent
print pages to the bottom.
|
| getTitleRows |
returns the range that is specified as title rows range.
|
| setTitleRows |
specifies a range of rows as title rows range.
|
| Methods' Details |
getPrintAreas
- Description
- returns a sequence containing all print areas of the sheet.
|
|
setPrintAreas
- Description
- sets the print areas of the sheet.
If none of the sheets in a document have print areas,
the whole sheets are printed. If any sheet contains print areas,
other sheets without print areas are not printed.
- Parameter aPrintAreas
- a sequence containing all print areas for this sheet.
|
|
getPrintTitleColumns
| boolean |
| getPrintTitleColumns(); |
- Description
- returns, whether the title columns are repeated on all subsequent
print pages to the right.
|
|
setPrintTitleColumns
| void |
| setPrintTitleColumns( |
[in] boolean |
bPrintTitleColumns ); |
- Description
- specifies whether the title columns are repeated on all subsequent
print pages to the right.
- Parameter bPrintTitleColumns
- if true, title columns are repeated on each page.
|
|
getTitleColumns
- Description
- returns the range that is specified as title columns range.
Title columns can be automatically repeated on all subsequent
print pages to the right, using
XPrintAreas::setPrintTitleColumns.
- Returns
- the range of columns that is specified as title columns range.
|
|
setTitleColumns
- Description
- specifies a range of columns as title columns range.
The rows of the passed range are ignored.
Title columns can be automatically repeated on all subsequent
print pages to the right, using
XPrintAreas::setPrintTitleColumns.
- Parameter aTitleColumns
- the title columns range.
|
|
getPrintTitleRows
| boolean |
| getPrintTitleRows(); |
- Description
- returns, whether the title rows are repeated on all subsequent
print pages to the bottom.
|
|
setPrintTitleRows
| void |
| setPrintTitleRows( |
[in] boolean |
bPrintTitleRows ); |
- Description
- specifies whether the title rows are repeated on all subsequent
print pages to the bottom.
- Parameter bPrintTitleRows
- if true, title rows are repeated on each page.
|
|
getTitleRows
- Description
- returns the range that is specified as title rows range.
Title rows can be automatically repeated on all subsequent
print pages to the bootom, using
XPrintAreas::setPrintTitleRows.
- Returns
- the range of rows that is specified as title rows range.
|
|
setTitleRows
- Description
- specifies a range of rows as title rows range.
The columns of the passed range are ignored.
Title rows can be automatically repeated on all subsequent
print pages to the bottom, using
XPrintAreas::setPrintTitleRows.
- Parameter aTitleRows
- the title rows range.
|
|
Copyright © 2013, The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache, the Apache feather logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache Software Foundation. Other names may be trademarks of their respective owners.


Here are
{% if type == 'sad' %}
your most sad and negative songs from your library
{% else %}
your most upbeat and happy songs from your library
{% endif %}
!
Depending on the amount of your songs stored in your library it may take up to a few minutes.
Therefore the amount of songs is limited to the last 500 by default.


Design Before Coding Kanban
The first post in this three-part series focused on gathering requirements before spending time coding. While it is not necessary, I recommend that everyone read part 1 (Gathering Requirements). Understanding and having clear “User Stories” outlining the intended purpose of a tool is crucial, especially as we move towards building our new tool.
Once our “User Stories” have been defined and agreed upon by all stakeholders, we then need to begin breaking them down into tasks. There are many different methodologies that allow us to track these different tasks. Part 2 of this three-part series will focus on one of them; Kanban.
I use Kanban daily, both personally and professionally. If you want to understand the principles of Kanban, then I recommend that you start with this Wikipedia page. No matter what methodology or process you use, having a consistent and repeatable utility is a must.
This post will go over using Kanban both digitally and manually, but first you must understand the general purpose of Kanban. Tracking our work can be difficult, especially with the use of E-mail, Slack, Skype, Teams, Yammer, HipChat, etc. etc. The constant communication that is available to us is overwhelming, but having a central location that you can organize your “To-Do’s” or tasks is necessary. Not for our management or organizations tracking purposes, it is so that we can track exactly what we need to do next.
The theory of Kanban is to visually identify items that need to be worked on. Kanban allows you to understand what tasks need to be worked on, which ones are in-progress, and which ones are complete. Using this information, we begin to identify any blockers or obstacles that may need to be fixed so that an item/task can move from “To Do” to “Done”. This principle helps us identify our WIP (Work in Progress) so that the flow between “gates” or “hand-off points” is as smooth and controlled as possible. Think of this like an assembly line:
Let’s say we have two workers in an assembly line. The first person’s job is to paint a car door handle, the second person’s job is to install that door handle on a new car. If the first person can paint 5 handles in 10 minutes, but the second person takes 10 minutes to install the handle; we have a problem. This means that we either need to increase staff that install car door handles or maybe the same person should do both.
Understanding these blockers will help us identify gaps in our processes, or the lack of labor to accomplish our goals.  I have listed a few below that are both free and paid. In my professional life, I use Jira’s Kanban feature. In my personal life, I use both a whiteboard with post-it notes and built-in features of GitHub Projects (example):
If you just do a quick google search for “free Kanban tools” or go to GitHub.com and search for “Kanban” you will find many open source projects that you can host yourself. If you don’t want to host it yourself, then check out DigitalOcean.com. If you think a digital tool would work for you, you can even use Outlook (here or here) or Gmail to manage your tasks in the Kanban style.I’m not sure about you, but I personally carry a leather-bound notebook (with DoanePaper) with me wherever I go. Whether at work, out with friends, going to bed, etc., I always have my notebook. In my opinion a digital tool is great, but I’m faster at writing things down on paper than I am opening an app. Plus, I always have it with me.
Another option or addition is by using a whiteboard in your home or work office. The first thing you do is draw some columns. Typically, you have three different columns: To-Do, In-Progress, and Done. Starting out you will have everything in your To-Do column. As you begin a new task you move that sticky-note to the In-Progress column. If that item gets blocked or cannot be completed, you should move it back to the To-Do column. You should only have a few items In-Progress (ideally, you would only have one). Once you have completed that task, you move it to the Done column.
That’s it! Kanban allows you to visually see tasks and progress you are making on your projects. The manual process is great for a single person or a team that is in close quarters. If you’re spread out or in a cubicle this may not work as well. This is where having a platform like Jira or Trello really shines. Especially for teams that are global or in different locations.
Kanban is powerful, yet extremely simple. Using a tool to manage your tasks so that you understand exactly what you, your team, and others are working on reduces potential re-work while also making sure that all tasks for a project are complete (and on-time). The third post in this series I will take the concepts of both post one and two, and we will begin to breakdown our User Stories onto our Kanban board. Remember, we have not started coding yet. Next, we will design how our stakeholders may use our new tool. Understanding this, will speed up our development time and reduce re-work.


HUỲNH THANH DANH
As you probably already notice, I am Danh. I am currently working as a Sr. Engineer for Spiraledge, Inc.
WORK EXPERIENCE
AUG 2021 >> today
Spiraledge, Inc | Frontend developer
- Project: Tend - farm management software
- Technology: angularjs, Angular@8, d3.js
AUG 2017 >> AUG 2021
Lac Viet Computing Corp | Team Leader
- Project: SureHIS - Hospital Infomation System
- Technology: Angular 11, Tailwind Css, Ant Design
MAY 2016 >> AUG 2017
Construction Join Stock Company - Cofico | Sharepoint Developer
- Project: eOffice - Specialized Portals
- Technology: Sharepoint Server 2013, Kendo jQuery
DEC 2013 >> MAY 2016
Lac Viet Computing Corp | Sharepoint Developer
- Project: SureLMS - Learning Management System
- Technology: Sharepoint Server 2010, MsSQL Server 2008
- Project: SureLRN - Learning Management System
- Technology: Webform Asp.NET 4.5
MAY 2013 >> NOV 2013
ILA VietName | Sharepoint Developer
- Project: ILA Portal
- Technology: Sharepoint Server 2010


This simple struct contains Cartesian coordinates specified by integers x,y,z.
More...
#include <Utils.h>
|
| | Coords () |
| | Default constructor that creates an empty Coords object. More...
|
| |
| | Coords (const int xval, const int yval, const int zval) |
| | Constructor that creates a Coords object with the x,y,z coordinates set using the input values xval, yval, and zval. More...
|
| |
| void | setXYZ (const int xval, const int yval, const int zval) |
| | Sets the x,y,z coordinates using the input values xval, yval, and zval. More...
|
| |
| bool | operator== (const Coords &rhs) const |
| | Defines the conditions when two Coords structs are deemed to be equal. More...
|
| |
| bool | operator!= (const Coords &rhs) const |
| | Defines the conditions when two Coords structs are deemed to be unequal. More...
|
| |
|
| int | x |
| | The x Cartesian coordinate. More...
|
| |
| int | y |
| | The y Cartesian coordinate. More...
|
| |
| int | z |
| | The z Cartesian coordinate. More...
|
| |
This simple struct contains Cartesian coordinates specified by integers x,y,z.
- Copyright
- MIT License. For more information, see the LICENSE file that accompanies this software package.
- Author
- Michael C. Heiber
- Date
- 2017-2019
◆ Coords() [1/2]
| KMC_Lattice::Coords::Coords |
( |
| ) |
|
|
inline |
Default constructor that creates an empty Coords object.
◆ Coords() [2/2]
| KMC_Lattice::Coords::Coords |
( |
const int |
xval, |
|
|
const int |
yval, |
|
|
const int |
zval |
|
) |
| |
|
inline |
Constructor that creates a Coords object with the x,y,z coordinates set using the input values xval, yval, and zval.
- Parameters
-
| xval | is the input x value. |
| yval | is the input y value. |
| zval | is the input z value. |
◆ operator!=()
| bool KMC_Lattice::Coords::operator!= |
( |
const Coords & |
rhs | ) |
const |
|
inline |
Defines the conditions when two Coords structs are deemed to be unequal.
- Parameters
-
| rhs | is the right hand side Coords struct of the comparison operator. |
◆ operator==()
| bool KMC_Lattice::Coords::operator== |
( |
const Coords & |
rhs | ) |
const |
|
inline |
Defines the conditions when two Coords structs are deemed to be equal.
- Parameters
-
| rhs | is the right hand side Coords struct of the comparison operator. |
◆ setXYZ()
| void KMC_Lattice::Coords::setXYZ |
( |
const int |
xval, |
|
|
const int |
yval, |
|
|
const int |
zval |
|
) |
| |
|
inline |
Sets the x,y,z coordinates using the input values xval, yval, and zval.
- Parameters
-
| xval | is the input x value. |
| yval | is the input y value. |
| zval | is the input z value. |
| int KMC_Lattice::Coords::x |
The x Cartesian coordinate.
| int KMC_Lattice::Coords::y |
The y Cartesian coordinate.
| int KMC_Lattice::Coords::z |
The z Cartesian coordinate.
The documentation for this struct was generated from the following file:


Inversion at unit circle in the complex plane:
f(z)=1/z, where z=x+iy.
Add complex conjugation to get a true mirror image.
Put the center of inversion at w=u+iv.
Use a radius R for the circle.
f(z) = w + (R2 / |z - w |2) (z - w).
Very close to the circle:
same as a mirror image at the tangent line.
Similarities far away:
- The images of circles and lines are circles and lines.
- A circle that intersects at a right angle is mapped onto itself.
- The inside of such a circle is mapped onto itself.
The image of small region is a linear transform:
Mirroring, translation, rotation and isotropic scaling.
Scaling factor (Lyapunov coefficient):
R2 / |z - w |2.
Multiple circle inversions can strongly expand or shrink pixels.


betterFORM provides several components for installation. Only choosen components will be downloaded and installed.
For a quick install choose the components betterFORM standalone and Forms and follow the install instructions. After installation finishs step into the install directory and execute betterform.jar
The betterFORM project. If no other component is selected, betterFORM is installed as web application archive (WAR file) at the choose directory.
The betterFORM standalone component installs an embeded Apache Jetty server betterFORM runs in. After installation switch to the choosen install directory and execute betterform.jar to start the server
The betterFORM XRX component installs betterForm and eXist as a ready to go XRX platform. After installation switch to the choosen install directory and execute startup.sh/startup.bat from the bin directory
The eXist-admin-password for now ist 'betterform'
adds all JavaScript sources uncompiled for full debug capabilities. betterFORM recommends Firebug as client side debugging tool
This installs the betterForm's demo, reference and test forms. To browse and run the forms point your browser to* http://localhost:8080/betterform/jsp/forms.jsp
The W3C XForms Conformance Test Suite. Browse and execute the tests by pointing your browser to* http://localhost:8080/betterform/jsp/forms.jsp?forms/XFormsTestSuite1.1E1/Edition1
* assuming you run betterFORM within the embedded Jetty Server. If you deploy betterFORM into your own Servlet Container you have to adjust the URLs to the server and port betterFORM runs in


<%= (!!locals.user.profile)?user:'' %>
<%if( locals.user == ''){%>
Login
<%}else{%>
>
<%=user.profile.name%>
<%}%>
Sign in
Become a guide
I want to go to
sometime in
March
.


the blog
tales from DBC
previous entries
- first
- second
- third
- fourth
- fifth
- sixth
- seventh
- eigth
- ninth
- ten
- eleven
- twelve
- thirteen
- fourteen
- fifteen
- sixteen
April 25th - Classes vs. Modules
It's easy to get classes and modules confused. They share many similar characteristics. For example, both classes and modules are identified by capitalizing their first letter.  However, there are key difference.
Classes, as you probably already know, are usually created to serve a single purpose. If you are modeling a motorcycle, for example, you'd create classes to represent each motorcycle part. You would have a motor class, a wheel class, a seat class, a frame class, and so on. Within each class are methods that define its functionality. A motor class will have an on/off method and a cylinder method. A wheel class will have a turn method and a brake method. These methods determine how each instance of a motor class or wheel class behaves and interacts with other objects.
Modules can be looked at as a supporting partner of classes.  However, these methods aren't intended for a specific object's use. A module's methods can be used across multiple objects and classes. As such, you cannot instantiate a module. There can be no module object that acts as a receiver for module methods.
However, a module's methods can be used by other classes objects. The way this is achieved is by adding the module to a class. For example, let's say I have a module that provides a method to add a bunch of metal spikes to something. And let's say I am modeling a medieval knight. I can use that module, called the Spike module, in multiple types of classes. Using the include method, I can add Spike's methods to a flail class, for example. Or a helmet class.
The capability modules have to be added to multiple different classes, and therefore used by any number of objects, is a defining feature. The act of adding a modules behaviors to a class is called "mixing in." So you would say that modules have mix-in capability.
The second big defining feature of modules is that they provide namespaces. This vague term simply means that they provide a way to distinguish between similarly named methods. For example, if a Smart module has a think method, and a Dumb module also has a think method, the fact that "think" has the same method name isn't a problem. By specifying which namespace (module) think is a part of, the differeing functionalities between Dumb think and Smart think won't be confused.
This is a lot of information, and I am still wrapping my head around it. The two resources I've found that have been most helpful in learning about modules and classes are:


Swe-SE-SCI scholars: Click on a header to sort by the corresponding column.
|
Scholar |
Affiliation |
#Publ. |
SCI ratio |
1st ratio |
SSS contrib. |
SSS rating |
Apparent research interests |
Signature SSS works |
|
Claes Wohlin |
Blekinge Institute of Technology |
176 |
0.39 |
0.31 |
24.98 |
63.2 |
empirical, project, success, journals, factors, analysis, methods, reliability, systematic, data |
2015: Towards a decision-making structure for selecting a research design in empirical software engineering. (Empirical Software Engineering)
2015: A general theory of software engineering: Balancing human, social and organizational capitals. (J. Syst. Softw.)
2013: Systematic literature reviews in software engineering. (Inf. Softw. Technol.)
2013: On the reliability of mapping studies in software engineering. (J. Syst. Softw.)
2011: Taking novelty to a new level. (Inf. Softw. Technol.)
2009: An analysis of the most cited articles in software engineering journals - 2002. (Inf. Softw. Technol.)
2008: An analysis of the most cited articles in software engineering journals - 2001. (Inf. Softw. Technol.)
2007: Most cited journal articles in software engineering. (Inf. Softw. Technol.)
2007: An analysis of the most cited articles in software engineering journals - 2000. (Inf. Softw. Technol.)
2005: Most cited journal articles in software engineering. (Inf. Softw. Technol.)
2005: An analysis of the most cited articles in software engineering journals - 1999. (Inf. Softw. Technol.)
2004: Are Individual Differences in Software Development Performance Possible to Capture Using a Quantitative Survey?. (Empirical Software Engineering)
2003: Prioritizing and Assessing Software Project Success Factors and Project Characteristics using Subjective Data. (Empirical Software Engineering)
2001: Assessing Project Success Using Subjective Evaluation Factors. (Softw. Qual. J.)
2000: Subjective evaluation as a tool for learning from software project success. (Inf. Softw. Technol.)
1999: Strategies for industrial relevance in software engineering education. (J. Syst. Softw.)
1995: Soft factors and their impact on time to market. (Softw. Qual. J.)
1995: An Experimental Evaluation of Capture-Recapture in Software Inspections. (Softw. Test. Verification Reliab.)
1994: Certification of Software Components. (IEEE Trans. Software Eng.)
|
|
Jan Bosch |
Chalmers / Gothenburg University |
332 |
0.13 |
0.31 |
12.59 |
53.52 |
product, architecture, lines, ecosystems, object, variability, families, development, data, component |
2018: Ecosystem traps and where to find them. (J. Softw. Evol. Process.)
2012: Software ecosystems: Taking software development beyond the boundaries of the organization. (J. Syst. Softw.)
2011: Introducing agile customer-centered development in a legacy software product line. (Softw. Pract. Exp.)
2010: From integration to composition: On the impact of software product lines, global development and ecosystems. (J. Syst. Softw.)
2003: Software architecture - Engineering quality attributes. (J. Syst. Softw.)
1999: Superimposition: a component adaptation technique. (Inf. Softw. Technol.)
|
|
Per Runeson |
Lund University |
143 |
0.29 |
0.21 |
8.72 |
36.8 |
testing, test, unit, open, industry, inspection, collaboration, academia, product, detection |
2014: Variation factors in the design and analysis of replicated controlled experiments - Three (dis)similar studies on inspections versus unit testing. (Empirical Software Engineering)
2009: Guidelines for conducting and reporting case study research in software engineering. (Empirical Software Engineering)
2003: Test processes in software product evolution - a qualitative survey on the state of practice. (J. Softw. Maintenance Res. Pract.)
1998: An Experimental Evaluation of an Experience-Based Capture-Recapture Method in Software Code Inspections. (Empirical Software Engineering)
|
|
Emilia Mendes |
Blekinge Institute of Technology |
176 |
0.15 |
0.4 |
11.39 |
33.35 |
web, effort, estimation, company, applications, cost, hypermedia, bayesian, improve, value |
2020: When to update systematic literature reviews in software engineering. (J. Syst. Softw.)
2018: Towards improving decision making and estimating the value of decisions in value-based software engineering: the VALUE framework. (Softw. Qual. J.)
2008: Replicating studies on cross- vs single-company effort models using the ISBSG Database. (Empirical Software Engineering)
2008: Cross-company vs. single-company web effort models using the Tukutuku database: An extended study. (J. Syst. Softw.)
2008: Bayesian Network Models for Web Effort Prediction: A Comparative Study. (IEEE Trans. Software Eng.)
2005: Investigating Web size metrics for early Web cost estimation. (J. Syst. Softw.)
2003: A Comparative Study of Cost Estimation Models for Web Hypermedia Applications. (Empirical Software Engineering)
1998: Reusability and maintainability in hypermedia applications for education. (Inf. Softw. Technol.)
|
|
Benoit Baudry |
KTH Royal Institute of Technology |
190 |
0.18 |
0.12 |
6.76 |
29.31 |
test, model, testability, design, automatic, testing, genetic, validation, optimization, improving |
2005: Measuring design testability of a UML class diagram. (Inf. Softw. Technol.)
2005: From genetic to bacteriological algorithms for mutation-based testing. (Softw. Test. Verification Reliab.)
|
|
Tony Gorschek |
Blekinge Institute of Technology |
114 |
0.44 |
0.12 |
11.04 |
26.56 |
requirements, model, empirical, product, process, management, transfer, practice, abstraction, development |
2014: On the use of software design models in software development practice: An empirical investigation. (J. Syst. Softw.)
2012: Introduction of a process maturity model for market-driven product management and requirements engineering. (J. Softw. Maintenance Res. Pract.)
2008: Requirements engineering: In search of the dependent variables. (Inf. Softw. Technol.)
2007: A controlled empirical evaluation of a requirements abstraction model. (Inf. Softw. Technol.)
2006: Requirements Abstraction Model. (Requir. Eng.)
2004: Packaging software process improvement issues: a method and a case study. (Softw. Pract. Exp.)
|
|
Robert Feldt |
Chalmers / Gothenburg University |
120 |
0.27 |
0.14 |
4.98 |
24.74 |
test, search, genetic, programming, diverse, diversity, empirical, cases, versions, testing |
2010: Links between the personalities, views and attitudes of software engineers. (Inf. Softw. Technol.)
|
|
Miroslaw Staron |
Chalmers / Gothenburg University |
127 |
0.15 |
0.35 |
10.18 |
23.53 |
measurement, industrial, development, systems, large, projects, model, defect, method, measures |
2018: Industrial experiences from evolving measurement systems into self-healing systems for improved availability. (Softw. Pract. Exp.)
2016: MeSRAM - A method for assessing robustness of measurement programs in large software development organizations and its industrial evaluation. (J. Syst. Softw.)
2012: Critical role of measures in decision processes: Managerial and technical measures in the context of large software development organizations. (Inf. Softw. Technol.)
2011: Developing measurement systems: an industrial case study. (J. Softw. Maintenance Res. Pract.)
2010: A method for forecasting defect backlog in large streamline software development projects and its industrial evaluation. (Inf. Softw. Technol.)
2009: A framework for developing measurement systems and its industrial evaluation. (Inf. Softw. Technol.)
2008: Predicting weekly defect inflow in large software projects based on project planning and test status. (Inf. Softw. Technol.)
2006: Empirical assessment of using stereotypes to improve comprehension of UML models: A set of experiments. (J. Syst. Softw.)
|
|
Björn Regnell |
Lund University |
89 |
0.33 |
0.18 |
6.2 |
22.99 |
requirements, quality, model, mobile, scale, testing, large, domain, scenario, reqt |
2001: An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software. (Requir. Eng.)
2000: Are the Perspectives Really Different? - Further Experimentation on Scenario-Based Reading of Requirements. (Empirical Software Engineering)
2000: Towards integration of use case modelling and usage-based testing. (J. Syst. Softw.)
|
|
Michael Felderer |
Blekinge Institute of Technology |
167 |
0.1 |
0.31 |
7.61 |
21.57 |
testing, risk, security, test, industrial, defect, system, requirements, systems, results |
2019: Comprehensibility of system models during test design: a controlled experiment comparing UML activity diagrams and state machines. (Softw. Qual. J.)
2016: Risk orientation in software testing processes of small and medium enterprises: an exploratory and comparative study. (Softw. Qual. J.)
2016: Model-based security testing: a taxonomy and systematic classification. (Softw. Test. Verification Reliab.)
2015: Manual test case derivation from UML activity diagrams and state machines: A controlled experiment. (Inf. Softw. Technol.)
2014: Integrating risk-based testing in industrial test processes. (Softw. Qual. J.)
|
|
Krzysztof Wnuk |
Blekinge Institute of Technology |
93 |
0.2 |
0.3 |
7.14 |
20.92 |
requirements, decision, management, scoping, large, scale, industrial, open, visualization, innovation |
2016: Supporting Scope Tracking and Visualization for Very Large-Scale Requirements Engineering-Utilizing FSC+, Decision Patterns, and Atomic Decision Visualizations. (IEEE Trans. Software Eng.)
2015: Exploring factors affecting decision outcome and lead time in large-scale requirements engineering. (J. Softw. Evol. Process.)
2014: Bridges and barriers to hardware-dependent software ecosystem participation - A case study. (Inf. Softw. Technol.)
2013: Obsolete software requirements. (Inf. Softw. Technol.)
2012: Replication of an experiment on linguistic tool support for consolidation of requirements from multiple sources. (Empirical Software Engineering)
|
|
Martin Monperrus |
KTH Royal Institute of Technology |
90 |
0.27 |
0.18 |
6.66 |
20.83 |
model, measurement, automated, automatic, system, repair, modèles, detecting, calls, surveillance |
2013: Automated measurement of models of requirements. (Softw. Qual. J.)
2013: Detecting missing method calls as violations of the majority rule. (ACM Trans. Softw. Eng. Methodol.)
2012: What should developers be aware of? An empirical study on the directives of API documentation. (Empirical Software Engineering)
2011: Model-driven generative development of measurement software. (Software and Systems Modeling)
|
|
Martin Höst |
Lund University |
94 |
0.19 |
0.21 |
7.06 |
18.45 |
product, source, processes, development, management, project, open, commercial, systematic, knowledge |
2011: A systematic review of research on open source software in commercial software product development. (Inf. Softw. Technol.)
2001: Exploring bottlenecks in market-driven requirements management processes with discrete event simulation. (J. Syst. Softw.)
2000: Using Students as Subjects-A Comparative Study of Students and Professionals in Lead-Time Impact Assessment. (Empirical Software Engineering)
2000: Evaluation of code review methods through interviews and experimentation. (J. Syst. Softw.)
1997: A subjective effort estimation experiment. (Inf. Softw. Technol.)
|
|
Jürgen Börstler |
Blekinge Institute of Technology |
75 |
0.2 |
0.37 |
4.8 |
17.71 |
teaching, role, object, play, learning, concepts, projects, programs, pedagogies, programmieren |
2016: Beauty and the Beast: on the readability of object-oriented example programs. (Softw. Qual. J.)
2016: The Role of Method Chains and Comments in Software Readability and Comprehension - An Experiment. (IEEE Trans. Software Eng.)
1995: Integrated software reuse: Management and techniques : Paul Walton and Neil Maiden (eds) Ashgate Publishing, Hants, UK (1993) 178 pp 49.50 hardcover ISBN 1 85742 146 9. (Inf. Softw. Technol.)
|
|
Ivica Crnkovic |
Chalmers / Gothenburg University |
144 |
0.09 |
0.28 |
5.31 |
16.75 |
component, systems, development, embedded, scm, process, components, management, change, predictability |
2011: A Classification Framework for Software Component Models. (IEEE Trans. Software Eng.)
2005: Automated Component-Based Software Engineering. (J. Syst. Softw.)
2002: Challenges of component-based development. (J. Syst. Softw.)
|
|
Daniel Méndez Fernández |
Blekinge Institute of Technology |
78 |
0.18 |
0.28 |
7.44 |
15.94 |
requirements, artefact, naming, pain, practice, results, germany, improvement, first, design |
2019: Empirical software engineering: From discipline to interdiscipline. (J. Syst. Softw.)
2019: Artefacts in software engineering: a fundamental positioning. (Software and Systems Modeling)
2017: Naming the pain in requirements engineering - Contemporary problems, causes, and effects in practice. (Empirical Software Engineering)
2015: Naming the pain in requirements engineering: A design for a global family of surveys and first results from Germany. (Inf. Softw. Technol.)
2015: Artefact-based requirements engineering: the AMDiRE approach. (Requir. Eng.)
2012: Field study on requirements engineering: Investigation of artefacts, project parameters, and execution strategies. (Inf. Softw. Technol.)
|
|
Darja Smite |
Blekinge Institute of Technology |
70 |
0.17 |
0.5 |
6.28 |
15.26 |
global, development, learned, lessons, offshoring, coordination, cost, evidence, empirical, agile |
2017: Software teams and their knowledge networks in large-scale software development. (Inf. Softw. Technol.)
2014: An empirically based terminology and taxonomy for global software engineering. (Empirical Software Engineering)
2013: Offshore insourcing in software development: Structuring the decision-making process. (J. Syst. Softw.)
2012: Lessons learned from transferring software products to India. (J. Softw. Evol. Process.)
2010: Empirical evidence in global software engineering: a systematic review. (Empirical Software Engineering)
|
|
Mikael Svahnberg |
Blekinge Institute of Technology |
32 |
0.41 |
0.59 |
9.59 |
14.61 |
quality, architecture, attributes, product, architectures, method, requirements, consensus, building, identifying |
2017: A model for assessing and re-assessing the value of software reuse. (J. Softw. Evol. Process.)
2015: Uni-REPM: a framework for requirements engineering process assessment. (Requir. Eng.)
2013: Uni-REPM: validated and improved. (Requir. Eng.)
2010: A systematic review on strategic release planning models. (Inf. Softw. Technol.)
2007: Six years of evaluating software architectures in student projects. (J. Syst. Softw.)
2005: An Investigation of a Method for Identifying a Software Architecture Candidate with Respect to Quality Attributes. (Empirical Software Engineering)
2005: A taxonomy of variability realization techniques. (Softw. Pract. Exp.)
2004: An industrial study on building consensus around software architectures and quality attributes. (Inf. Softw. Technol.)
1999: Evolution in software product lines: two cases. (J. Softw. Maintenance Res. Pract.)
|
|
Eric Knauss |
Chalmers / Gothenburg University |
98 |
0.11 |
0.32 |
3.77 |
13.8 |
requirements, continuous, supporting, clarification, anforderungen, agile, system, ecosystems, feedback, heuristic |
2018: Continuous clarification and emergent requirements flows in open-commercial software ecosystems. (Requir. Eng.)
2015: Patterns of continuous requirements clarification. (Requir. Eng.)
|
|
Markus Borg |
RISE Research Institutes of Sweden |
59 |
0.19 |
0.42 |
5.18 |
13.71 |
traceability, impact, reports, analysis, information, issue, change, context, bug, time |
2019: Selecting component sourcing options: A survey of software engineering's broader make-or-buy decisions. (Inf. Softw. Technol.)
2017: Supporting Change Impact Analysis Using a Recommendation System: An Industrial Case Study in a Safety-Critical Context. (IEEE Trans. Software Eng.)
2016: TuneR: a framework for tuning software engineering tools with hands-on instructions in R. (J. Softw. Evol. Process.)
2014: Recovering from a decade: a systematic mapping of information retrieval approaches to software traceability. (Empirical Software Engineering)
|
|
Patrizio Pelliccione |
Chalmers / Gothenburg University |
132 |
0.14 |
0.06 |
4.74 |
12.79 |
systems, cars, framework, specifications, architectural, component, evolution, beyond, chairs, sequences |
2009: CHARMY: A Framework for Designing and Verifying Architectural Specifications. (IEEE Trans. Software Eng.)
2008: An architectural approach to the correct and automatic assembly of evolving component-based systems. (J. Syst. Softw.)
|
|
Efi Papatheocharous |
RISE Research Institutes of Sweden |
53 |
0.19 |
0.49 |
4.13 |
12.65 |
cost, estimation, decision, artificial, fuzzy, neural, networks, development, agile, systems |
2018: The GRADE taxonomy for supporting decision-making of asset selection in software-intensive system development. (Inf. Softw. Technol.)
2017: An investigation of effort distribution among development phases: A four-stage progressive software cost estimation model. (J. Softw. Evol. Process.)
2014: Empirical evidence and state of practice of software agile teams. (J. Softw. Evol. Process.)
|
|
Federico Ciccozzi |
Mälardalen University |
66 |
0.14 |
0.44 |
5.97 |
11.96 |
systems, model, uml, embedded, models, code, generation, execution, modelling, complex |
2019: Execution of UML models: a systematic review of research and practice. (Software and Systems Modeling)
2018: On the automated translational execution of the action language for foundational UML. (Software and Systems Modeling)
2018: Architecture optimization: speed or accuracy? both! (Softw. Qual. J.)
2016: Explicit connection patterns (ECP) profile and semantics for modelling and generating explicit connections in complex UML composite structures. (J. Syst. Softw.)
2013: Round-trip support for extra-functional property management in model-driven engineering of embedded systems. (Inf. Softw. Technol.)
|
|
Gregory Gay |
Chalmers / Gothenburg University |
31 |
0.32 |
0.65 |
6.61 |
11.94 |
test, generation, real, coverage, search, model, program, automated, faults, steering |
2017: Automated Steering of Model-Based Test Oracles to Admit Real Program Behaviors. (IEEE Trans. Software Eng.)
2016: The Effect of Program and Model Structure on the Effectiveness of MC/DC Test Adequacy Coverage. (ACM Trans. Softw. Eng. Methodol.)
2015: The Risks of Coverage-Directed Test Case Generation. (IEEE Trans. Software Eng.)
2015: Automated Oracle Data Selection Support. (IEEE Trans. Software Eng.)
2010: Finding robust solutions in requirements models. (Autom. Softw. Eng.)
2010: Automatically finding the control variables for complex system behavior. (Autom. Softw. Eng.)
|
|
Emelie Engström |
Lund University |
32 |
0.34 |
0.41 |
5.81 |
11.54 |
test, regression, testing, line, product, selection, systematic, empirical, industrial, taxonomy |
2020: How software engineering research aligns with design science: a review. (Empirical Software Engineering)
2017: SERP-test: a taxonomy for supporting industry-academia communication. (Softw. Qual. J.)
2013: Test overlay in an emerging software product line - An industrial case study. (Inf. Softw. Technol.)
2011: Software product line testing - A systematic mapping study. (Inf. Softw. Technol.)
2010: A systematic review on regression test selection techniques. (Inf. Softw. Technol.)
|
|
Wasif Afzal |
Mälardalen University |
62 |
0.15 |
0.21 |
5.03 |
10.28 |
systematic, runtime, testing, fault, megamodelling, complex, systems, framework, megam, test |
2016: Software test process improvement approaches: A systematic literature review and an industrial case study. (J. Syst. Softw.)
2015: An experiment on the effectiveness and efficiency of exploratory testing. (Empirical Software Engineering)
2014: Prediction of faults-slip-through in large software projects: an empirical evaluation. (Softw. Qual. J.)
2009: A systematic review of search-based testing for non-functional system properties. (Inf. Softw. Technol.)
|
|
Michael Unterkalmsteiner |
Blekinge Institute of Technology |
32 |
0.34 |
0.28 |
5.81 |
10.15 |
requirements, improvement, process, alignment, test, systematic, retrieval, scale, measurement, literature |
2016: Large-scale information retrieval in software engineering - an experience report from industrial application. (Empirical Software Engineering)
2015: Assessing requirements engineering and software test alignment - Five case studies. (J. Syst. Softw.)
2014: A conceptual framework for SPI evaluation. (J. Softw. Evol. Process.)
2014: A taxonomy for requirements engineering and software test alignment. (ACM Trans. Softw. Eng. Methodol.)
2012: Evaluation and Measurement of Software Process Improvement - A Systematic Literature Review. (IEEE Trans. Software Eng.)
|
|
Nauman Bin Ali |
Blekinge Institute of Technology |
21 |
0.48 |
0.48 |
6.51 |
10.08 |
systematic, simulation, search, literature, industrial, process, reviews, testing, assisted, industry |
2019: On the search for industry-relevant regression testing research. (Empirical Software Engineering)
2019: A critical appraisal tool for systematic literature reviews in software engineering. (Inf. Softw. Technol.)
2018: Reliability of search in systematic reviews: Towards a quality assessment framework for the automated-search strategy. (Inf. Softw. Technol.)
2016: FLOW-assisted value stream mapping in the early phases of large-scale software development. (J. Syst. Softw.)
2015: Evaluation of simulation-assisted value stream mapping for software product development: Two industrial cases. (Inf. Softw. Technol.)
2014: A systematic literature review on the industrial use of software process simulation. (J. Syst. Softw.)
|
|
Regina Hebig |
Chalmers / Gothenburg University |
58 |
0.14 |
0.33 |
4.0 |
10.05 |
model, evolution, development, mde, languages, processes, transformation, xtend, complex, impact |
2017: The changing balance of technology and process: A case study on a combined setting of model-driven development and classical C coding. (J. Softw. Evol. Process.)
2017: On the complex nature of MDE evolution and its impact on changeability. (Software and Systems Modeling)
2017: Approaches to Co-Evolution of Metamodels and Models: A Survey. (IEEE Trans. Software Eng.)
|
|
Richard Berntsson-Svensson |
Chalmers / Gothenburg University |
44 |
0.18 |
0.45 |
4.76 |
9.9 |
requirements, quality, quper, practice, industrial, companies, model, creativity, techniques, investigation |
2017: Is role playing in Requirements Engineering Education increasing learning outcome? (Requir. Eng.)
2013: An investigation of how quality requirements are specified in industrial practice. (Inf. Softw. Technol.)
2012: Setting quality targets for coming releases with QUPER: an industrial case study. (Requir. Eng.)
2012: Quality Requirements in Industrial Practice - An Extended Interview Study at Eleven Companies. (IEEE Trans. Software Eng.)
|
|
Jennifer Horkoff |
Chalmers / Gothenburg University |
97 |
0.07 |
0.39 |
6.1 |
9.35 |
goal, modeling, requirements, analysis, interactive, models, model, systematic, enterprise, experiences |
2019: Creative goal modeling for innovative requirements. (Inf. Softw. Technol.)
2019: Goal-oriented requirements engineering: an extended systematic mapping study. (Requir. Eng.)
2016: Interactive goal model analysis for early requirements engineering. (Requir. Eng.)
2014: Strategic business modeling: representation and reasoning. (Software and Systems Modeling)
2013: Comparison and evaluation of goal-oriented satisfaction analysis techniques. (Requir. Eng.)
|
|
Riccardo Scandariato |
Chalmers / Gothenburg University |
67 |
0.13 |
0.16 |
3.28 |
9.29 |
security, design, learned, distributed, networks, securechange, automated, logical, systems, lifelong |
2015: A descriptive study of Microsoft's threat modeling technique. (Requir. Eng.)
2014: Predicting Vulnerable Software Components via Text Mining. (IEEE Trans. Software Eng.)
|
|
Björn Lundell |
Skövde University |
71 |
0.1 |
0.31 |
3.14 |
9.17 |
open, source, tool, method, standards, swedish, perceptions, systems, experiences, companies |
2011: Practitioner perceptions of Open Source software in the embedded systems area. (J. Syst. Softw.)
2004: Changing perceptions of CASE technology. (J. Syst. Softw.)
|
|
Elizabeth Bjarnason |
Lund University |
30 |
0.23 |
0.7 |
6.33 |
8.89 |
requirements, distances, development, evidence, practices, cases, gaps, method, large, timelines |
2019: Improving requirements-test alignment by prescribing practices that mitigate communication gaps. (Empirical Software Engineering)
2017: The role of distances in requirements communication: a case study. (Requir. Eng.)
2016: A theory of distances in software engineering. (Inf. Softw. Technol.)
2016: A multi-case study of agile requirements engineering and the use of test cases as requirements. (Inf. Softw. Technol.)
2014: Challenges and practices in aligning requirements with verification and validation: a case study of six companies. (Empirical Software Engineering)
2012: Are you biting off more than you can chew? A case study on causes and effects of overscoping in large-scale software engineering. (Inf. Softw. Technol.)
|
|
Davide Fucci |
Blekinge Institute of Technology |
42 |
0.17 |
0.38 |
4.65 |
8.75 |
test, development, replication, effects, sleep, first, external, requirements, conformance, impact |
2020: Need for Sleep: The Impact of a Night of Sleep Deprivation on Novice Developers' Performance. (IEEE Trans. Software Eng.)
2017: A Dissection of the Test-Driven Development Process: Does It Really Matter to Test-First or to Test-Last? (IEEE Trans. Software Eng.)
2015: Towards an operationalization of test-driven development skills: An industrial empirical study. (Inf. Softw. Technol.)
2014: On the role of tests in test-driven development: a differentiated and partial replication. (Empirical Software Engineering)
|
|
Mauro Caporuscio |
Linneaus Univerity |
47 |
0.13 |
0.66 |
5.51 |
8.34 |
service, middleware, applications, pervasive, systems, networking, time, run, subscribe, performance |
2017: Building design-time and run-time knowledge for QoS-based component assembly. (Softw. Pract. Exp.)
2016: GoPrime: A Fully Decentralized Middleware for Utility-Aware Service Assembly. (IEEE Trans. Software Eng.)
2015: Engineering Future Internet applications: The Prime approach. (J. Syst. Softw.)
2007: Model-based system reconfiguration for dynamic performance management. (J. Syst. Softw.)
2003: Design and Evaluation of a Support Service for Mobile, Wireless Publish/Subscribe Applications. (IEEE Trans. Software Eng.)
|
|
Pontus Johnson |
KTH Royal Institute of Technology |
90 |
0.07 |
0.26 |
2.34 |
8.33 |
analysis, architecture, theory, modeling, probabilistic, enterprise, general, business, extended, attack |
2016: The Tarpit - A general theory of software engineering. (Inf. Softw. Technol.)
|
|
Antonio Cicchetti |
Mälardalen University |
75 |
0.08 |
0.35 |
3.09 |
8.08 |
model, evolution, web, development, systems, applications, view, models, weaving, managing |
2019: Multi-view approaches for software and system modelling: a systematic literature review. (Software and Systems Modeling)
2013: Managing the evolution of data-intensive Web applications by model-driven techniques. (Software and Systems Modeling)
|
|
Panagiota Chatzipetrou |
Örebro University |
20 |
0.35 |
0.55 |
3.53 |
7.97 |
analysis, component, framework, data, statistical, requirements, prioritization, goals, attributes, effort |
2020: Component attributes and their importance in decisions and component selection. (Softw. Qual. J.)
2015: A multivariate statistical framework for the analysis of software effort phase distribution. (Inf. Softw. Technol.)
2015: An experience-based framework for evaluating alignment of software quality goals. (Softw. Qual. J.)
|
|
Thorsten Berger |
Chalmers / Gothenburg University |
78 |
0.08 |
0.22 |
4.02 |
7.92 |
variability, modeling, feature, management, systems, efficiency, domain, large, industry, models |
2020: The state of adoption and the challenges of systematic variability management in industry. (Empirical Software Engineering)
2014: Variability mechanisms in software ecosystems. (Inf. Softw. Technol.)
2013: A Study of Variability Models and Languages in the Systems Software Domain. (IEEE Trans. Software Eng.)
|
|
Fabian Fagerholm |
Blekinge Institute of Technology |
41 |
0.15 |
0.39 |
3.65 |
7.74 |
projects, agile, education, experience, continuous, patterns, lean, onboarding, developers, source |
2018: Designing and implementing an environment for software start-up education: Patterns and anti-patterns. (J. Syst. Softw.)
2017: The RIGHT model for Continuous Experimentation. (J. Syst. Softw.)
2015: Performance Alignment Work: How software developers experience the continuous adaptation of team performance in Lean and Agile environments. (Inf. Softw. Technol.)
|
|
Mira Kajko-Mattsson |
KTH Royal Institute of Technology |
105 |
0.05 |
0.72 |
5.1 |
7.61 |
maintenance, model, management, process, problem, corrective, cm3, agile, maturity, eliciting |
2005: A Survey of Documentation Practice within Corrective Maintenance. (Empirical Software Engineering)
2004: Problems within front-end support. (J. Softw. Maintenance Res. Pract.)
2002: Problem management maturity within corrective maintenance. (J. Softw. Maintenance Res. Pract.)
2000: Software problem reporting and resolution process at ABB Robotics AB: state of practice. (J. Softw. Maintenance Res. Pract.)
|
|
Philipp Leitner |
Chalmers / Gothenburg University |
113 |
0.05 |
0.21 |
2.57 |
7.57 |
service, services, cloud, violations, level, web, testing, performance, practice, compositions |
2019: A mixed-method empirical study of Function-as-a-Service software development in industrial practice. (J. Syst. Softw.)
|
|
Emil Alégroth |
Blekinge Institute of Technology |
27 |
0.22 |
0.52 |
3.51 |
7.35 |
testing, gui, visual, industrial, practice, test, empirical, debt, testware, automated |
2017: On the long-term use of visual gui testing in industrial practice: a case study. (Empirical Software Engineering)
2016: Maintenance of automated test suites in industry: An empirical study on Visual GUI Testing. (Inf. Softw. Technol.)
2015: Visual GUI testing in practice: challenges, problemsand limitations. (Empirical Software Engineering)
|
|
Birgit Penzenstadler |
Chalmers / Gothenburg University |
103 |
0.05 |
0.42 |
2.38 |
7.29 |
sustainability, requirements, systems, design, model, domain, systematic, green, automotive, system |
2018: Sustainability analysis and ease of learning in artifact-based requirements engineering: The newest member of the family of studies (It's a girl!). (Inf. Softw. Technol.)
|
|
Jakob Axelsson |
RISE Research Institutes of Sweden |
64 |
0.08 |
0.58 |
2.89 |
7.18 |
systems, system, time, embedded, real, architecting, automotive, analysis, hardware, architectural |
2016: Quality assurance in software ecosystems: A systematic literature mapping and research agenda. (J. Syst. Softw.)
2014: Characteristics of software ecosystems for Federated Embedded Systems: A case study. (Inf. Softw. Technol.)
|
|
Ulrik Franke |
RISE Research Institutes of Sweden |
72 |
0.07 |
0.38 |
3.87 |
6.92 |
enterprise, architecture, insurance, cyber, service, analysis, framework, availability, bayesian, trees |
2018: What can we learn from enterprise architecture models? An experiment comparing models and documents for capability development. (Software and Systems Modeling)
2014: An architecture framework for enterprise IT service availability analysis. (Software and Systems Modeling)
2012: Availability of enterprise IT systems: an expert-based Bayesian framework. (Softw. Qual. J.)
|
|
Helena Holmström Olsson |
Malmö University |
95 |
0.05 |
0.33 |
3.2 |
6.62 |
embedded, data, ecosystem, mind, praise, telesm, online, cost, management, paying |
2020: Going digital: Disruption and transformation in software-intensive embedded systems ecosystems. (J. Softw. Evol. Process.)
2017: From ad hoc to strategic ecosystem management: the "Three-Layer Ecosystem Strategy Model" (TeLESM). (J. Softw. Evol. Process.)
|
|
Jan-Philipp Steghöfer |
Chalmers / Gothenburg University |
70 |
0.07 |
0.27 |
2.05 |
6.51 |
systems, self, agile, organising, open, die, scrum, organic, computing, evolutionary |
2017: No silver brick: Opportunities and limitations of teaching Scrum with Lego workshops. (J. Syst. Softw.)
|
|
Robert Lagerström |
KTH Royal Institute of Technology |
78 |
0.06 |
0.27 |
4.83 |
6.32 |
architecture, enterprise, systems, analysis, modifiability, cost, maintainability, metamodel, models, measuring |
2013: Increasing software development efficiency and maintainability for complex industrial systems - A case study. (J. Softw. Evol. Process.)
2012: Identifying factors affecting software development cost and productivity. (Softw. Qual. J.)
2010: Architecture analysis of enterprise systems modifiability - Models, analysis, and validation. (J. Syst. Softw.)
2010: Architecture analysis of enterprise systems modifiability: a metamodel for software change cost estimation. (Softw. Qual. J.)
|
|
Hannes Holm |
KTH Royal Institute of Technology |
40 |
0.1 |
0.55 |
2.56 |
5.5 |
attacks, vulnerability, system, expert, investigation, empirical, security, scanning, application, web |
2015: A Bayesian network model for likelihood estimations of acquirement of critical software vulnerabilities and exploits. (Inf. Softw. Technol.)
2014: Automatic data collection for enterprise architecture models. (Software and Systems Modeling)
|
|
Peter Fritzson |
Linköping University |
124 |
0.03 |
0.19 |
3.4 |
5.17 |
object, language, modeling, modelica, environment, debugging, equation, system, openmodelica, incremental |
1994: Using assertions in declarative and operational models for automated debugging. (J. Syst. Softw.)
1983: Symbolic debugging through incremental compilation in an integrated environment. (J. Syst. Softw.)
|
|
Barbara Gallina |
Mälardalen University |
74 |
0.05 |
0.34 |
2.0 |
5.17 |
safety, process, reuse, lines, model, 26262, systems, iso, analysis, enabling |
2020: Quantitative evaluation of tailoring within SPICE-compliant security-informed safety-oriented process lines. (J. Softw. Evol. Process.)
|
|
Bestoun S. Ahmed |
Karlstad University |
23 |
0.17 |
0.43 |
3.29 |
4.9 |
testing, interaction, combinatorial, swarm, particle, systematic, aware, automated, optimization, applications |
2017: Handling constraints in combinatorial interaction testing in the presence of multi objective particle swarm and multithreading. (Inf. Softw. Technol.)
2015: Achievement of minimized combinatorial test suite for configuration-aware software functional testing using the Cuckoo Search algorithm. (Inf. Softw. Technol.)
2011: A variable strength interaction test suites generation strategy using Particle Swarm Optimization. (J. Syst. Softw.)
|
|
Jonas Lundberg |
Linneaus Univerity |
61 |
0.05 |
0.28 |
1.78 |
4.2 |
analysis, response, resilience, design, points, air, cognitive, work, traffic, precise |
2009: Fast and precise points-to analysis. (Inf. Softw. Technol.)
|
|
Ludwik Kuzniarz |
Blekinge Institute of Technology |
27 |
0.11 |
0.56 |
1.44 |
4.06 |
uml, models, model, multimedia, teaching, development, initial, modeling, domain, stereotypes |
2011: Empirical extension of a classification framework for addressing consistency in model based development. (Inf. Softw. Technol.)
|
|
Francis Palma |
Linneaus Univerity |
20 |
0.15 |
0.7 |
1.37 |
4.06 |
detection, antipatterns, specification, patterns, soa, prioritization, restful, linguistic, service, test |
2019: UniDoSA: The Unified Specification and Detection of Service Antipatterns. (IEEE Trans. Software Eng.)
|
|
Mariam Kamkar |
Linköping University |
28 |
0.11 |
0.39 |
2.35 |
4.05 |
slicing, dynamic, interprocedural, debugging, program, programs, applied, algorithmic, testing, preface |
1998: Application of program slicing in algorithmic debugging. (Inf. Softw. Technol.)
1995: An overview and comparative classification of program slicing techniques. (J. Syst. Softw.)
|
|
Gul Calikli |
Chalmers / Gothenburg University |
26 |
0.12 |
0.38 |
1.43 |
4.04 |
confirmation, bias, effects, analysis, company, experience, modeling, empirical, factors, developers |
2015: Empirical analysis of factors affecting confirmation bias levels of software engineers. (Softw. Qual. J.)
|
|
Lars Pareto |
Chalmers / Gothenburg University |
26 |
0.12 |
0.35 |
2.33 |
4.0 |
architectural, empirical, design, base, development, concern, projects, concerns, model, investigation |
2012: Collaborative prioritization of architectural concerns. (J. Syst. Softw.)
2012: Concern coverage in base station development: an empirical investigation. (Software and Systems Modeling)
|
|
Jonas Gamalielsson |
Skövde University |
32 |
0.09 |
0.5 |
2.39 |
3.96 |
open, source, standards, biological, beyond, evolutionary, communities, digital, w3c, gene |
2015: On organisational influences in software standards and their open source implementations. (Inf. Softw. Technol.)
2014: Sustainability of Open Source software communities beyond a fork: How and why has the LibreOffice project evolved? (J. Syst. Softw.)
|
|
Francisco Gomes de Oliveira Neto |
Chalmers / Gothenburg University |
20 |
0.15 |
0.5 |
2.27 |
3.91 |
test, support, testing, requirements, empirical, distributed, scale, tasks, evaluate, aligning |
2019: Evolution of statistical analysis in empirical software engineering research: Current state and steps forward. (J. Syst. Softw.)
2016: Full modification coverage through automatic similarity-based test case selection. (Inf. Softw. Technol.)
|
|
Kenneth Lind |
Chalmers / Gothenburg University |
13 |
0.23 |
0.69 |
1.3 |
3.84 |
size, estimation, components, embedded, automated, code, time, real, compsize, model |
2012: A Practical Approach to Size Estimation of Embedded Software Components. (IEEE Trans. Software Eng.)
|
|
Deepika Badampudi |
Blekinge Institute of Technology |
11 |
0.27 |
0.82 |
2.18 |
3.83 |
systematic, knowledge, translation, decision, making, literature, oss, scale, synthesis, perspectives |
2018: A decision-making process-line for selection of software asset origins and components. (J. Syst. Softw.)
2016: Software component decision-making: In-house, OSS, COTS or outsourcing - A systematic literature review. (J. Syst. Softw.)
|
|
Thomas Olsson |
RISE Research Institutes of Sweden |
40 |
0.07 |
0.35 |
1.57 |
3.82 |
decision, gqm, making, system, language, time, quality, companies, requirements, reconfigurable |
2019: An empirical study on decision making for quality requirements. (J. Syst. Softw.)
|
|
Jelena Zdravkovic |
Stockholm University |
89 |
0.03 |
0.27 |
2.06 |
3.79 |
business, capability, service, processes, requirements, modeling, governance, enterprise, services, frameworks |
2015: Capturing consumer preferences as requirements for software product lines. (Requir. Eng.)
|
|
Birgitta Lindström |
Skövde University |
20 |
0.15 |
0.4 |
2.27 |
3.79 |
mutants, mutation, time, real, strong, systems, dynamic, aspect, subsuming, testability |
2019: On strong mutation and the theory of subsuming logic-based mutants. (Softw. Test. Verification Reliab.)
2017: Using mutation to design tests for aspect-oriented models. (Inf. Softw. Technol.)
|
|
Javier Gonzalez-Huerta |
Blekinge Institute of Technology |
35 |
0.09 |
0.17 |
1.52 |
3.74 |
product, architecture, derivation, multimodel, validating, model, improvement, models, quality, integrating |
2015: Validating a model-driven software architecture evaluation and improvement method: A family of experiments. (Inf. Softw. Technol.)
|
|
Kristian Sandahl |
Linköping University |
28 |
0.21 |
0.07 |
1.72 |
3.53 |
participation, inspections, replication, expert, knowledge, active, assessing, systems, developing, methods |
1998: An Extended Replication of an Experiment for Assessing Methods for Software Requirements Inspections. (Empirical Software Engineering)
|
|
Pasqualina Potena |
RISE Research Institutes of Sweden |
32 |
0.09 |
0.16 |
1.49 |
3.37 |
tradeoff, functional, attributes, optimization, service, directions, architecture, quality, composition, systems |
2013: Optimization of adaptation plans for a service-oriented architecture with cost, reliability, availability and performance tradeoff. (J. Syst. Softw.)
|
|
Görel Hedin |
Lund University |
78 |
0.03 |
0.27 |
1.86 |
3.33 |
attribute, grammars, programming, preface, extreme, jastadd, object, languages, incremental, design |
2005: Teaching extreme programming to large groups of students. (J. Syst. Softw.)
|
|
Imed Hammouda |
Chalmers / Gothenburg University |
73 |
0.03 |
0.32 |
1.81 |
3.14 |
open, source, patterns, design, concern, pattern, development, communities, systems, sustainable |
2009: Design profiles: toward unified tool support for design patterns and UML profiles. (Softw. Pract. Exp.)
|
|
Saad Mubeen |
Mälardalen University |
69 |
0.03 |
0.58 |
2.67 |
3.03 |
analysis, time, systems, end, embedded, response, timing, component, distributed, vehicular |
2019: Supporting timing analysis of vehicular embedded systems through the refinement of timing constraints. (Software and Systems Modeling)
2015: Integrating mixed transmission and practical limitations with the worst-case response-time analysis for Controller Area Network. (J. Syst. Softw.)
|
|
Niklas Lavesson |
Jönköping University |
54 |
0.04 |
0.24 |
1.62 |
2.99 |
learning, end, user, agreements, license, spyware, approve, online, rule, inducer |
2014: A method for evaluation of learning components. (Autom. Softw. Eng.)
|
|
Narges Khakpour |
Linneaus Univerity |
20 |
0.1 |
0.75 |
1.28 |
2.81 |
systems, self, adaptive, formal, behavioral, synthesis, control, modeling, structural, analysis |
2012: HPobSAM for modeling and analyzing IT Ecosystems - Through a case study. (J. Syst. Softw.)
|
|
Muhammad Ovais Ahmad |
Karlstad University |
17 |
0.12 |
0.53 |
2.15 |
2.75 |
kanban, development, agile, systematic, companies, lean, empirical, transition, practices, management |
2018: Kanban in software engineering: A systematic mapping study. (J. Syst. Softw.)
2017: An empirical study of portfolio management and Kanban in agile and lean software companies. (J. Softw. Evol. Process.)
|
|
Christin Lindholm |
Lund University |
8 |
0.25 |
0.75 |
2.06 |
2.57 |
risk, development, medical, device, analysis, process, management, perspective, identification, testing |
2015: Involving user perspective in a software risk management process. (J. Softw. Evol. Process.)
2014: A case study on software risk analysis and planning in medical device development. (Softw. Qual. J.)
|
|
Ana Magazinius |
RISE Research Institutes of Sweden |
9 |
0.22 |
0.67 |
2.07 |
2.55 |
estimation, cost, distortional, distortions, organizational, effects, bounty, complexity, confirming, exploring |
2012: Investigating intentional distortions in software cost estimation - An exploratory study. (J. Syst. Softw.)
2010: Software cost estimation inhibitors - a case study in automotive context. (J. Softw. Maintenance Res. Pract.)
|
|
Patrik Berander |
Malmö University |
7 |
0.29 |
0.71 |
1.15 |
2.53 |
requirements, prioritization, cumulative, hierarchies, hierarchical, voting, two, efficient, measurement, management |
2009: Evaluating two ways of calculating priorities in requirements hierarchies - An experiment on hierarchical cumulative voting. (J. Syst. Softw.)
|
|
Cyrille Artho |
KTH Royal Institute of Technology |
85 |
0.02 |
0.55 |
1.93 |
2.5 |
model, checking, testing, analysis, networked, java, static, test, applications, programs |
2003: High-level data races. (Softw. Test. Verification Reliab.)
|
|
Niklas Mellegård |
RISE Research Institutes of Sweden |
13 |
0.08 |
0.69 |
1.12 |
1.47 |
defect, automotive, weight, improving, impact, efficiency, reports, initial, scheme, classification |
2016: Impact of Introducing Domain-Specific Modelling in Software Maintenance: An Industrial Case Study. (IEEE Trans. Software Eng.)
|
|
Michael Mattsson |
Blekinge Institute of Technology |
13 |
0.08 |
0.54 |
1.12 |
1.45 |
framework, industrial, solutions, experience, application, frameworks, causes, evolving, evolution, paper |
2000: Stability assessment of evolving industrial object-oriented frameworks. (J. Softw. Maintenance Res. Pract.)
|
|
Daniel Flemström |
Mälardalen University |
8 |
0.12 |
0.75 |
1.07 |
1.33 |
test, guarded, passive, assertions, interactive, saga, natural, prioritization, reuse, cases |
2018: Similarity-based prioritization of test case automation. (Softw. Qual. J.)
|
|
Francesco Flammini |
Linneaus Univerity |
45 |
0.02 |
0.42 |
1.44 |
1.32 |
systems, critical, security, surveillance, modelling, infrastructure, infrastructures, multiformalism, physical, repairable |
2009: Automatic instantiation of abstract tests on specific configurations for large critical control systems. (Softw. Test. Verification Reliab.)
|
|
Peter Wallin |
RISE Research Institutes of Sweden |
11 |
0.09 |
0.27 |
1.1 |
1.27 |
development, related, system, issues, vehicles, architecting, architectures, architecture, heavy, automotive |
2012: Problems and their mitigation in system and software architecting. (Inf. Softw. Technol.)
|
|
Stefan Cedergren |
RISE Research Institutes of Sweden |
4 |
0.25 |
0.25 |
1.03 |
1.0 |
products, performance, development, evaluating |
2014: Evaluating performance in the development of software-intensive products. (Inf. Softw. Technol.)
|


Create User Form
First Name:
Last Name:
Email:
Password:
Tracker 1:
ID:
Nick:
Tracker 2:
ID:
Nick:
Tracker 3:
ID:
Nick:


Enter your password criteria below:
Use either field to set a specific length. Or both to select a length at random, from a range.


1 Furthermore, Amasis dedicated, besides monuments of marvellous size in all the other temples of note, the huge image that lies supine before Hephaestus' temple at Memphis; this image is seventy-five feet in length; there stand on the same base, on either side of the great image, two huge statues hewn from the same block, each of them twenty feet high.
2 There is at Saïs another stone figure of like size, supine as is the figure at Memphis. It was Amasis, too, who built the great and most marvellous temple of Isis at Memphis.


Name: brib
hobbys: eat,fly,sandbathe play with toys, flap wings, hunt for worms, make nest.
Date: 9/14/21
plan for raids
this is where our attacks from the news will go
rabid attacks on the humans. make sure to take the bread!?
attack humans!, take bread!, eat bread!, repeat!.


Sector Overview
NPO "Insight"
US Non-Profit Sector | 501c(3)
(Kinda-Not-Really) Predictive Analytics
kinda
Small NPOs
Projected Significant Contributions
Projected Contributions in Grants
Compute
Expected Revenue
{{pred_small}}
Medium-Sized NPOs
Projected Functional Expenses
Compute
Expected Revenue
{{pred_med}}
Large-Sized NPOs
Projected Functional Expenses
Compute
Expected Revenue
{{pred_large}}


Class UnicastData
A unicast data message is sent when a client sends data directly to another client.
Implements
Inherited Members
Namespace: JetBlack.MessageBus.Messages
Assembly: JetBlack.MessageBus.Messages.dll
Syntax
public class UnicastData : Message, IEquatable<UnicastData>
Constructors
| Improve this Doc View SourceUnicastData(Guid, String, String, Boolean, DataPacket[])
Construct the message.
Declaration
public UnicastData(Guid clientId, string feed, string topic, bool isImage, DataPacket[] dataPackets)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Guid | clientId | The id of the client. |
| System.String | feed | The name of the feed. |
| System.String | topic | The name of the topic. |
| System.Boolean | isImage | If true the data is considered complete. |
| DataPacket[] | dataPackets | The data packets. |
Properties
| Improve this Doc View SourceClientId
The is of the client.
Declaration
public Guid ClientId { get; }
Property Value
| Type | Description |
|---|---|
| System.Guid |
DataPackets
The data packets.
Declaration
public DataPacket[] DataPackets { get; }
Property Value
| Type | Description |
|---|---|
| DataPacket[] |
Feed
The name of the feed.
Declaration
public string Feed { get; }
Property Value
| Type | Description |
|---|---|
| System.String |
IsImage
If true the data is considered complete.
Declaration
public bool IsImage { get; }
Property Value
| Type | Description |
|---|---|
| System.Boolean |
Topic
The name of the topic.
Declaration
public string Topic { get; }
Property Value
| Type | Description |
|---|---|
| System.String |
Methods
| Improve this Doc View SourceEquals(UnicastData)
Test for equality.
Declaration
public bool Equals(UnicastData other)
Parameters
| Type | Name | Description |
|---|---|---|
| UnicastData | other | The message to compare. |
Returns
| Type | Description |
|---|---|
| System.Boolean | True if the messages are the same. |
Equals(Object)
Test for equality.
Declaration
public override bool Equals(object obj)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Object | obj | The object to compare. |
Returns
| Type | Description |
|---|---|
| System.Boolean | True if the objects are equal. |
Overrides
GetHashCode()
Returns the hash code for this instance.
Declaration
public override int GetHashCode()
Returns
| Type | Description |
|---|---|
| System.Int32 | A 32-bit signed integer hash code. |
Overrides
ReadBody(DataReader)
Read the body of the message.
Declaration
public static UnicastData ReadBody(DataReader reader)
Parameters
| Type | Name | Description |
|---|---|---|
| DataReader | reader | The reader. |
Returns
| Type | Description |
|---|---|
| UnicastData | The message |
ToString()
Converts the value of the current object to it's equivalent string representation.
Declaration
public override string ToString()
Returns
| Type | Description |
|---|---|
| System.String | A string representation of the current object. |
Overrides
| Improve this Doc View SourceWrite(DataWriter)
Write a message.
Declaration
public override DataWriter Write(DataWriter writer)
Parameters
| Type | Name | Description |
|---|---|---|
| DataWriter | writer | The message writer. |
Returns
| Type | Description |
|---|---|
| DataWriter | The message writer. |


National Covid Info
State of Texas Covid Info
Official CDC Resources
Johns Hopkins National Case Map


Wavelets prove ineffective in our process since we found we lacked the necessary frequency resolution to determing vowel sounds or pitch. Perhaps sampling at higher than 8khz would give better results, but the processing cost needed to pursue higher sampling rates led us other methods...
Formants analysis is an effective way of analyzing vowel sounds regardless of speaker. If we were able to build an extraction program, we would have been well on our way to processing whole words and not just vowel sound.
Pitch determination is an semi-effective way of implementing speaker recognition. Our pitch determination process could be refined or could run in parallel with other speaker recognition methods to produce better results.


Full Bleed Images on Percentage Width Content
Sometimes you need to have a big ol' image all up in your page. If your content's container has a percentage width, you can use this mixin to break the image out of the container.
Check out the image below.

Currently, this only works for image with percentage widths.
Here is some junk content to push this down a bit further. Lorem ipsum dolor sit amet, consectetur adipisicing elit. Sequi, est. Repudiandae tenetur voluptate in dignissimos recusandae repellat blanditiis ipsa neque maxime laudantium a, est impedit doloremque quae autem unde consequatur.


Let us help apps determine location. This mean sending anonymus location data to us, even when no apps are running.


Welcome to pyhecdss’s documentation!¶
- pyhecdss
- Installation
- Usage
- Usage with examples
- Setting message level and program name
- Example of writing a DSS File
- Opening and closing a DSS File
- A regular time series
- An irregular time series
- Reading DSS Files
- Catalog filtering
- Reading Timeseries Data
- Closing DSS File
- Best way to work with DSS Files
- Convenience methods for matching partnames
- Use regular expressions for more powerful filtering
- Plotting and other features
- Discussion on PER-* and INST-* period types
- pyhecdss
- Contributing
- Credits
- CHANGELOG


Welcome to Code Quiz!
This is a knowledge quiz to check your understanding of Javascript, HTML and CSS.
Instructions:
-
Each question has multiple answers. Please choose the best answer.
-
You have 60 seconds to answer five questions before the quiz ends.


Controller : empno = {{emp.empno}}, empname = {{emp.empname}}
Ename :
Directive:1 Instance:1
Directive:1 Instance:2
Directive:2 Instance:1


JavaScript is disabled on your browser.
Skip navigation links
Overview
Package
Class
Use
Tree
Deprecated
Index
Help
Prev Letter
Next Letter
Frames
No Frames
All Classes
A
B
C
D
E
F
G
H
I
L
M
N
P
R
S
T
U
V
X
Y
L
lastName
- Variable in class application.models.
Customer
lblBookingSeatsTitle
- Variable in class application.controllers.
BookingController
lblDate
- Variable in class application.controllers.
BookingController
lblDate
- Variable in class application.controllers.
UserController
lblError
- Variable in class application.controllers.
FilmController
lblFailure
- Variable in class application.controllers.
BookingController
lblFailure
- Variable in class application.controllers.
CustomerController
lblFailure
- Variable in class application.controllers.
LoginController
lblFilmAge
- Variable in class application.controllers.
FilmController
lblFilmDescription
- Variable in class application.controllers.
FilmController
lblFilmTitle
- Variable in class application.controllers.
BookingController
lblFilmTitle
- Variable in class application.controllers.
FilmController
lblImageError
- Variable in class application.controllers.
FilmController
lblSeats
- Variable in class application.controllers.
BookingController
lblSuccess
- Variable in class application.controllers.
LoginController
lblTableInfo
- Variable in class application.controllers.
FilmController
lblTime
- Variable in class application.controllers.
BookingController
lblWelcome
- Variable in class application.controllers.
UserController
LOGGER
- Static variable in class application.
Main
loggerBegin(String, String)
- Method in class application.controllers.
MainController
loggerComplete(String, String)
- Method in class application.controllers.
MainController
LoginController
- Class in
application.controllers
Purpose: Control logging in to the program, and for setting up a User and their environment Description: Checks the user's username and password (via the Login view) and enables creation of Customer's (via the Registration view).
LoginController()
- Constructor for class application.controllers.
LoginController
logout()
- Method in class application.controllers.
MainController
A
B
C
D
E
F
G
H
I
L
M
N
P
R
S
T
U
V
X
Y
Skip navigation links
Overview
Package
Class
Use
Tree
Deprecated
Index
Help
Prev Letter
Next Letter
Frames
No Frames
All Classes


MUSIC_RECREQID_INVALID 739 test/test.c rec_id[0] != MUSIC_RECREQID_INVALID); MUSIC_RECREQID_INVALID 749 test/test.c rec_id[0] != MUSIC_RECREQID_INVALID); MUSIC_RECREQID_INVALID 759 test/test.c rec_id[0] != MUSIC_RECREQID_INVALID); MUSIC_RECREQID_INVALID 769 test/test.c rec_id[0] != MUSIC_RECREQID_INVALID); MUSIC_RECREQID_INVALID 773 test/test.c rec_id[1] != MUSIC_RECREQID_INVALID); MUSIC_RECREQID_INVALID 777 test/test.c rec_id[2] != MUSIC_RECREQID_INVALID);


In correspondence with one of my correspondents the other day, the subject of golf was raised. (There was a Herman Melville connection, with which I will not tax you.) This led me to recall a childhood memory, and I fired off an email as follows:
The only time in my life I ever played a round of golf was when I was eight years old. I was with a friend and his Scottish grandfather. My abiding memory of the adventure is that the grandfather whacked me on the elbow—hard—with his golf club. He insisted it was an accident. Hmm.
To which my correspondent replied:
Thanks for that piece of information—I am wondering whether the disclosure of the grandfather's nationality is a mere embellishment, or actually a key detail of the tale.
Without giving the matter much, or indeed any, thought, I replied immediately to say that I thought the detail highly significant. I have never played golf again.


I graduated from Amarillo college with a degree in Comptuer Information Systems with and emphasis on Cyber Security. I moved to Houston once I graduated. I Work in IT for about a year realized that I wanted to do more coding than hardware work. I have a passion for both but coding is what i like to do more.
HTML, CSS, HTML5, SASS & Bootstrap
JavaScript, React, Responsive Design, JQuery & JSON
RESTful API's, Git & Github
Microsoft Office Suite, Atom, Sublime
Ready to start your next Website? That's great! Give me a call or send me an email and I will get back to you as soon as possible!
806-584-4090


Why cooking gas is costly, by dealers - The Nation Newspaper
Emeka Ugwuanyi
THE Nigerian Association of Liquefied Petroleum Gas Marketers (NALPGAM) has blamed the continued hike in the price of cooking gas on exploitative activities by Liquefied Petroleum Gas (LPG) Terminal Owners and Off-takers.
Its Executive Secretary, Mr Bassey Essien in a statement issued at the weekend in Lagos said the increment had seen cooking gas price increase from between N2,600 and N3,000 in retail outlets to about 4,500 currently.
He said, “It has become necessary to bring to the attention of users of cooking gas, stakeholders in the industry and the Federal Government in particular to the level of exploitation that currently subsists in the pricing of cooking gas by terminal owners/off-takers.
Read Also: ‘Nigeria losing billions to gas flaring’
“The federal government approved the allocation of about 350,000MT of Gas per annum for local consumption through the Nigerian Liquefied Natural Gas (NLNG) company and this has been distributed through the terminals/off-takers to Gas Marketers who eventually distribute to end users.
“We noticed recently that gas delivered to terminals/off-takers which was being sold at N3,200,000 per 20 MT a week ago suddenly jumped to between N4,000,000 and N4,300,000 per 20MT at the terminals.”


No Information Required
LCRB has not requested any Personal History Summary forms for individuals associated with liquor related licences or applications at this time.
OUTSTANDING PERSONAL HISTORY FORMS
Each liquor licence associate must provide a completed Personal History Summary form along with required documents, including a copy of a recent Criminal Record Search performed by a local RCMP or police detachment.
The following associates have not provided completed personal history summary forms. The forms can be completed using the provided link, which can be emailed or sent by SMS to associates as needed:
| First Name | Last Name | DOB | Status | Action |
|---|---|---|---|---|
| {{item.firstName}} | {{item.lastName}} | {{item.birthdate | date : 'dd/MM/yyyy' : 'GMT'}} |
Not Submitted |
|
COMPLETED PERSONAL HISTORY FORMS
The following associates have completed their personal history summary forms. No further information is required at this time.
| First Name | Last Name | DOB | Date Submitted |
|---|---|---|---|
| {{item.firstName}} | {{item.lastName}} | {{item.birthdate | date : 'dd/MM/yyyy' : 'GMT'}} | {{item.dateSubmitted | date : 'short'}} |


new Passenger(config) → {object}
Passenger main constructor
Parameters:
| Name | Type | Description |
|---|---|---|
config |
object | configuration object with all necessary settings and options |
Properties:
| Name | Type | Description |
|---|---|---|
config.field |
string | the password field ID |
config.styles |
string | the custom CSS classes to be applied to the passenger box |
config.contracts |
array | the custom password contracts |
- Source:
Returns:
instance of Passenger
- Type
- object
Methods
(static) bAllPassed(sBoxID, bPassAll) → {boolean}
Are all contract rules passing?
Parameters:
| Name | Type | Description |
|---|---|---|
sBoxID |
string | unique id of the box |
bPassAll |
boolean | all rules passed |
- Source:
Returns:
are all the contract rules passing?
- Type
- boolean
(static) boxDisplayToggle(elAfter, box) → {DOMElement}
Toggles the display of the box
Parameters:
| Name | Type | Description |
|---|---|---|
elAfter |
DOMElement | the DOM element to create the toggle link after |
box |
DOMElement | the DOM element of the box |
- Source:
Returns:
the DOM element of the toggle link
- Type
- DOMElement
(static) createBox(elField, aContracts, config) → {DOMElement}
Create Passenger box for user feeback
Parameters:
| Name | Type | Description |
|---|---|---|
elField |
string | the ID of the specific instance of Passenger implementation |
aContracts |
array | array list of contracts |
config |
object | the configuration object passenger is instantiated with |
- Source:
Returns:
the newly created DOM element of the box
- Type
- DOMElement
(static) getContracts() → {array}
Get list of password rule contracts
- Source:
Returns:
array of contracts
- Type
- array
(static) getElement(selector) → {DOMElement}
Get the password element
Parameters:
| Name | Type | Description |
|---|---|---|
selector |
string | the string of the password field selector |
- Source:
Returns:
the DOM element of the password
- Type
- DOMElement
(static) inputTypeToggle(elField) → {DOMElement}
Toggle input type to password/text
Parameters:
| Name | Type | Description |
|---|---|---|
elField |
DOMElement | the DOM element of input |
- Source:
Returns:
the DOM element of input
- Type
- DOMElement
(static) setupBoxEvents(elField, box) → {DOMElement}
Set up all passbox events
Parameters:
| Name | Type | Description |
|---|---|---|
elField |
DOMElement | the DOM element of the input field |
box |
DOMElement | the DOM element of the passbox instance for field |
- Source:
Returns:
the DOM element of the input field
- Type
- DOMElement
(static) userEntry(e) → {void}
Examine the user input
Parameters:
| Name | Type | Description |
|---|---|---|
e |
event | the key event |
- Source:
Returns:
nothing
- Type
- void
isPassFulfilled() → {boolean}
Is the password contract requirements met for instance?
This:
- instance
- Source:
Returns:
whether password requirements have been met or not
- Type
- boolean


var io = require('socket.io').listen(8888);
var io = require('socket.io').listen(8888);
Register the connection.
io.sockets.on('connection', function(socket) {
Emit en event in order to say that the connection is active to the clients.
socket.emit('news', {
hello: 'world'
});
Listen to the events from tje client and acknolgge it.
socket.on('demo-client', function(data, fn) {
var jsonDate = new Date().toJSON();
console.log("The client called me at " + jsonDate, data);
if (fn !== undefined) {
Callback the emitter with any data you want to pass.
fn(jsonDate);
}
});
});


I'm a recent B.S. graduate of Florida Institute of Technology. My major was Computer Information Systems from Florida Tech's College of Engineering. Since I was a young boy I've been facinated with computers and always dreamed of one day working in the software developement field.


| No. | Station Name | Year | File Name | Description | Approved | Submitted By | {{scanannualrainfall.id}} | {{scanannualrainfall.station}} | {{scanannualrainfall.year}} | {{scanannualrainfall.FileRef | slice:12}} | {{scanannualrainfall.Description}} | False | True | {{scanannualrainfall.SY_SubmittedBy}} |
|---|


Places |
Documentation |
Tutorials |
JPLua plugins |
Configs |
For developers |
JA++ is a mod designed to be used instead of JA+
JA+ is no longer being developed and there are numerous issues, JA++ is is actively developed with contributions from the community making it suitable for many types of servers.
JA++ is not meant to be used with JA+, it is meant to replace it entirely. It is written in a way to be compatible with JA+.
This means you can use the JA++ client on a JA+ server, and a JA+ client on a JA++ server.
Please do not install JA+ before installing JA++ as it may result in conflicts.
Download JA++
with instructions
| Linux 32-bit | Linux 64-bit | Assets |
|---|---|---|
Places |
Documentation |
Tutorials |
JPLua plugins |
Configs |
For developers |


It’s a hard time on the blockchain right now, as we all know well. But even in such a bear market, our fabulous contributors still pulled through with some terrific posts. We appreciate them so much for this.
Staff Picks
Logo Design For Acrarium by @midun [graphics]
Acrarium is a backend for ACRA written in Java using Spring Boot, Vaadin and MySQL. The project owner made a request, asking volunteers to create a logo for them. Midun took the task on and created an cool, minimalistic logo using the letters “a” and “c”. He made sure the logo used colors linked to the project, and made sure the symbol works well as a small icon. This work deserves to be highlighted because it is well done both in terms of technical quality and in presentation.
Total payout: 17.24 STU Number of votes: 116
Building a Blockchain with Go - Part 9 - The Network Module by @tensor [video-tutorials]
This is the ninth part of a series on how to build a functional blockchain. Thus far, the series has addressed wallet modules, a transaction system and other functions. Now, @tensor deals with network interface, peer to peer, security and other functions of a healthy blockchain.
Total payout: 41.27 STU Number of votes: 122
French Translation |•| ReactOS Project |•| Part six|•| 1138 words by @yassinebad [translations]
This is the translator’s 6th contribution to the ReactOS project. From his post, you can see that he did an accurate translation this time as he learned from the mistakes made in the 5th contribution. He was also careful in making sure the translation was correct by doing research in understanding the the context of the sentences before determining the correct translation of each term. The translator works well with the advice given by the moderator @leyt.
Total payout: 32.43 STU Number of votes: 65
Steemfest 3: Utopian.io - Building a sustainable business on Steem by @techslut [blog]
The rare occasions when our CMO @techslut can find the time to write a major post are always a treat. This post, part of our #iamutopian series, covers her part of the Utopian presentation at Steemfest, and includes parts that were left out of the presentation due to time constraints. You should definitely check it out if you want to know what we’ve learned about building a business on this here blockchain.
Total payout: 67.83 STU Number of votes: 159
Writing a simple Compiler on my own - Action Rules for Declarations and Initializations [C][Flex][Bison] by @drifter1 [tutorials]
We’ve finally gotten our first run of the compiler that @drifter1 has been taking us through the process of building for the past few weeks. This is another great tutorial in this series, aiming at building a basic C compiler. With great process explanations, illustrations, and detailed content, @drifter1’s process always captures the reader’s attention. This is particularly impressive when targetting a topic that’s not as common nowadays, and complex to some extent. If you fancy such topics, make sure to check out this tutorial and the whole series so far!
Total payout: 31.99 STU Number of votes: 122
Utopian.io Post Statistics
The staff picked contributions are only a small (but exceptional) example of the mass of contributions reviewed and rewarded by Utopian.io.
- Overall, the last week saw a total of 197 posts, with 167 of them rewarded through an upvote by @utopian-io.
- In total, Utopian.io distributed an approximate of 4810.84 STU to contributors.
- The highest payout seen on any Utopian.io contribution this week was 249.207 STU, with a total of 673 votes received from the community.
- The contribution that attracted the most engagement was steemgg open source development update - - 2018.11.15, with no less than 10 comments in its comment threads.
- The average vote given by Utopian.io was worth 28.30 STU.
Category Statistics
|Category|Reviewed|Rewardable|Rewarded|Total rewards|Top contributor| |:-|:-|:-|:-|-:|:-| |bug-hunting|5|3|2|25.10 STU|@mightypanda| |graphics|7|4|4|120.43 STU|@teneresa| |tutorials|20|18|17|295.22 STU|@drifter1| |translations|64|62|59|1717.29 STU|@jubreal| |analysis|5|5|5|151.72 STU|@lostmine27| |development|33|32|31|1222.03 STU|@emrebeyler| |video-tutorials|5|4|4|127.12 STU|@tensor| |ideas|4|2|2|4.88 STU|@difelice5000| |blog|25|21|20|431.40 STU|@jaff8| |iamutopian|11|11|11|424.30 STU|@fego| |social|8|8|5|110.28 STU|@jingis07| |copywriting|1|1|1|1.62 STU|@ewuoso|
Join the community on Discord: https://discord.gg/azdmM3v
First Time Contributing in Utopian.io?
Learn how to contribute on our website
This page is synchronized from the post: Top of Utopian.io: November 14 - November 21


{% load staticfiles i18n %} {% comment %} Copyright (c) 2015-present, Philippine-California Advanced Research Institutes- The Village Base Station Project (PCARI-VBTS). All rights reserved. This source code is licensed under the BSD-style license found in the LICENSE file in the root directory of this source tree. {% endcomment %}


CSS (Cascading Style Sheets) are rules to describe how your HTML elements look. Writing good CSS is hard. It usually takes many years of experience and frustration of shooting yourself in the foot before one is able to write maintainable and scalable CSS. CSS, having a global namespace, is fundamentally designed for web documents, and not really for web apps that favor a components architecture. Hence, experienced front end developers have designed methodologies to guide people on how to write organized CSS for complex projects, such as using SMACSS, BEM, SUIT CSS, etc.
However, the encapsulation of styles that these methodologies bring about are artificially enforced by conventions and guidelines. They break the moment developers do not follow them.
As you might have realized by now, the front end ecosystem is saturated with tools, and unsurprisingly, tools have been invented to partially solve some of the problems with writing CSS at scale. “At scale” means that many developers are working on the same large project and touching the same stylesheets. There is no community-agreed approach on writing CSS in JS at the moment, and we are hoping that one day a winner would emerge, just like Redux did, among all the Flux implementations. For now, I would recommend CSS Modules. CSS modules is an improvement over existing CSS that aims to fix the problem of global namespace in CSS; it enables you to write styles that are local by default and encapsulated to your component. This feature is achieved via tooling. With CSS modules, large teams can write modular and reusable CSS without fear of conflict or overriding other parts of the app. However, at the end of the day, CSS modules are still being compiled into normal globally-namespaced CSS that browsers recognize, and it is still important to learn and understand how raw CSS works.
If you are a total beginner to CSS, Codecademy’s HTML & CSS course will be a good introduction to you. Next, read up on the Sass preprocessor, an extension of the CSS language which adds syntactic improvements and encourages style reusability. Study the CSS methodologies mentioned above, and lastly, CSS modules.
h1
,
div
, :before
), class/attribute selectors
(.btn
, [type="radio"]
), pseudo-classes
(:hover
) and ID selectors (#someElement
).
!important
) is used on a style
declaration, this declaration overrides any other declarations. Try
to avoid using !important
, as it breaks the natural
cascading in the stylesheets. Always look for a way to use
specificity before even considering !important
, and
only use !important on page-specific CSS that overrides foreign CSS
(from external libraries, like Bootstrap).
top
, right
,
bottom
, and left
properties would later
determine the final location of said positioned element.
static
relative
,
absolute
, fixed
, sticky
float
CSS property determines where an element should
be placed - along the left or right side of its container. This allows
text and inline elements to wrap around it. Also note, the element would
be removed from the normal flow of the web page, though still
remaining a part of the flow (in contrast to
position: absolute
). For an element to be
float
, it’s value must not be none
.
none
left
,
right
, inline-start
,
inline-end
.
clear
attribute
for more examples
TODO


--- layout: post title: "santa vs god" comments: true ---
give it a little thought. God is Santa for grownups, isn't it?


Besides the GeologicToolbox for ArcGIS Pro, additionally Java implementations which run independently from ArcGIS Pro are available. The Java code mainly addresses Java programmers (although principally everyone should be able to run them). To execute these helpers a suitable Java Runtime Environment and the current Java-code from the 52n Triturus project is needed.


Friday Night Hack Schedule
San Francisco
The event starts on Friday 7/19/13 and ends on 7/20/13
| 5 PM ↝ 7 PM | Opening Gathering |
|---|---|
| 7 PM ↝ 8.30 PM | Shabbat Dinner |
| 8.30 PM ↝ 9 PM | Pitching |
| 9 PM ↝ 12 AM | Hack |
| 12 AM ↝ 1 AM | Talk to Israel |
| 1 AM ↝ 1.30 AM | Midnight snack |
| 1 AM ↝ 5 AM | Hack / Chill |
| 5 AM ↝ 6 AM | Talk to Israel |
| 6 AM ↝ 7 AM | Hack |
| 7 AM ↝ 8 AM | Breakfast |
| 8 AM ↝ 10 AM | Hack |
| 10 AM ↝ 11 AM | Summary in Israel - Showcase in SF |
| 11 AM ↝ 2 PM | Lunch |
| 2 PM ↝ 4 PM | Break |
| 4 PM ↝ 7 PM | Hack |
| 7 PM ↝ 9 PM | Summary and a feedback session |
| 9 PM ↝ ∞ | PARTY! |


The Problem
The existing public transport doesn't pay enough attention to different special needs groups such as the visually impaired, children or the elderly. We want Helsinki to be the city where the people can use public transport smoothly regardless of age or capability. Currently, it is very difficult for visually impaired people to get the right bus to stop, especially during rush hour or if the bus is late. On the other hand, children can easily panic if they are not familiar with the route and the info screen with stop names is missing or faulty.
The Solution
The main purpose of the STOP 2.0 is to allow the traveller to give information for the driver about their wish to stop the bus. The application uses small iBeacon Bluetooth transmitters for location. Both the buses and the stops have iBeacon transmitters, so the user is able to identify the beacon and ask the bus to stop on the right place: either from the bus stop for the approaching vehicle or from inside the bus. STOP 2.0 is integrated into buses to notify the driver about the need to stop at a certain bus stop.


The Children’s workshop at The Roots India follows the ‘Play-way’ style of teaching by engaging them in play-like situations to develop their imagination and creative skills. Children are taught not only to use their minds but also their bodies thereby imparting in them expressive abilities and self-confidence. The workshop aims to train them not only for stage, but for leadership in life as well. These workshops for Acting are for Children of the age group 6 to 14 years.
No of Sessions: 8
Tuition Fee:
Per session duration: 2
Age criteria: 6-16 years
Schedule:
Direct Admission. No audition and interviews to be conducted
For registrations, contact us at therootssociety@gmail.com


Conversations
Posted on Fri 20 January 2017 in Learning
Let's talk about Chatbots
-
Users interact with the application built (by the client) that you implement.
-
The application can be a simple chat window or a mobile app, or even a robot with a voice interface.
The application sends the user input to the Conversation service.
-
The application connects to a workspace, which is a container for your dialog flow and training data.
-
The service interprets the user input, directs the flow of the conversation and gathers information that it needs.
-
You can connect additional Watson services to analyze user input, such as Tone Analyzer or Speech to Text.
The application can interact with your back-end systems based on the user's intent and additional information.
Implementation
The following steps need to be completed for an application:
- Configure a workspace: With the easy-to-use graphical environment, you set up the dialog flow and training data for your application.
- Develop your application :
- You code your application to connect to the Conversation workspace through API calls.
- You then integrate your app with other systems that you need, including back-end systems and third-party services such as chat services or social media.
Starting an application:
-
Log-in to Bluemix, Navigate to Conversation service, Create a Service and launch the tool.
-
Create Workspace :
3. Create Intents:
An intent represents the purpose of a user's input.
You can thinkg of intents as actions your users might want to perform with your application.
For example:
#hello
or `#goodbye
.
4. Building a Dialog:
A dialog defines the flow of your conversation in the form of a logic tree. Each node of the tree has a condition that triggers it, based on user input.
The whole conversation flow is directed using Dialogs.
5. Let's refine it!:
An entity definition includes a set of entity values that can be used to trigger different responses.
@entity
Each entity value can have multiple synonyms, which define different ways that the same value might be specified in user input.
Intents
Planning your intents:
Consider what your customers might want to do, and what the application is able to handle.
Choosing the correct intent for a user's input is the first step in providing a useful response.