Issue Tracking

1
Proprietary of SPEC Innovations® July 26, 2023 Dr. Steven Dam

Ask Us Your Questions
2
-Ask us your questions using the panel
on the right.
-This presentation is being recorded
and will be made available to you on
our website and through email.
-Contact us after the webinar through
● support@Innoslate.com
● Call 571.485.7800
● LinkedIn: “Innoslate Users and
Systems Engineers” Group
● Twitter: @specinnovations

Meet Your Host
• President and Founder of SPEC
Innovations
• Participated in the development of
C4ISR and DoDAF
• Expert Systems Engineering
Professionals Certificate
• steven.dam@specinnovations.com
• @stevenhdam
3

Agenda
• Transparent, SSoT
• Why is Issue Tracking Important?
• Issues vs. Requirements
• Transforming Requirements to Issues
• Collaboration & Tasking
• Monitoring Progress/Gap Analysis
4

Transparent, SSoT
• A “single source of truth” according to HubSpot “is a philosophy for
collecting data from across the enterprise and aggregating it into a central
repository.”
• The idea is that this provides transparency within your organization to
information
• DoD began with this idea, but has morphed it into the “authoritative source
of truth,” as they recognize that a central repository for their organization
is impossible and in fact undesirable for many reasons
• For issue tracking, a single source of truth may require duplication of
information in different tools, since each tool needs the information to
perform its functions
• As such, the SSoT for issue tracking really means a virtual “central
repository” that automatically synchronizes data sets between them
5

Why is Issue Tracking Important?
• In software development, issue
tracking refers to “the process of
monitoring software defects and
problems that arise before or after
deployment.
• In systems engineering, an issue is a
risk with a 100% probability of
occurrence (meaning it already
happened)
• Software tools, such as GitHub, Jira,
and GitLab, use issue tracking for not
only problems, but also for
requirements management
6

Issues vs. Requirements
• Issues that are problems require
an urgency to resolve them
• They can be bugs or useability
problems
• Requirements are the needs or
desires of a project formulated in
a way that expresses them clearly
to a developer
• Requirements and issues come
from many sources
7

Innoslate Enables the Transformation of
Requirements into Issues
• As functional requirements
are developed by the
systems engineers, those
requirements can be
pushed into GitHub for
software development
• Synchronizing and tracking
these requirements/issues
is critical
• SPEC Innovations has
automated this process
8

Collaboration: Pushing Requirements to GitHub
• As you hover over the
top right corner of the
Issue window, two
symbols show up
• + sign enables an
individual issue to be
created
• The up arrow enables an
upload of an entire
Innoslate document
9

Pushing Requirements to GitHub (continued)
• The up arrow dialog provides the means to
select the appropriate document
• You can also select the mode (Nested or Flat)
• Nested will take a decomposition and put
the children in GitHub as a check list
10

Pushing Requirements to GitHub (continued)
• As part of this process, an
Issue in Innoslate is
created and linked to the
GitHub issue via a web
hook
• The web hook allows
changes in the issue in
GitHub to update the issue
status in Innoslate
• Issues developed directly
in GitHub can also be
pushed to Innoslate for
tracking
11

Monitoring Software Development – SE
Perspective
• As software development
progresses, the systems
engineer is tasked with
monitoring the progress
• Innoslate provides a full
set of views to support the
monitoring efforts
• First, get your token from
GitHub, then select the
repository of interest
12

Perspective (continued)
• The overview provides
overall information
about:
• pull requests
• active issues
• recent open issues
• commits per week over
the last year
• Recent commits
13

• The Kanban Board
provides a means to
track progress of the
specific issues
• You can provide
comments
• Add labels
• Add assignees
(tasking)
14

• Issues provides a
means to search for
and add issues
• Author, Label, Sort
options
• Reminder: the
adding of issues
requires you to
hover over the right
corner of the “Open
Issues” bar
15

• Commits shows the
individual
commitments made
in most recent
order
• Commit Activity
shows the
commitments made
by developers over
past six months
16

• Gap analysis starts
with ensuring all the
traceability
relationships have
been established
• Then, using
Database View we
can track the status
of the requirements
and issues
17

Future Work Planned
• Now that we also have the links created between our testing tool
(Selenium) and Innoslate’s Test Center, we can update the status of
the requirements as well
• This next step will enhance issue tracking even more
18

19
Send in questions using the panel on the right.

Tuesday, August 15th, 2023 at 2:00 PM ET
Summer Intern Special
Mark Your
Calendars
20

SPEC Innovations
@SPECInnovations
Innoslate Users Group
Innoslate.com/blog
571.485.7800
innoslate.com
21
Thank you!
Visit cloud.innoslate.com for a trial.

GitHub Terminology
• Pull requests let you tell others about changes you've pushed to a
branch in a repository on GitHub
• Similar to saving a file that's been edited, a commit records
changes to one or more files in your branch. Git assigns each
commit a unique ID, called a SHA or hash, that identifies: The
specific changes
• Issues let you track your work on GitHub, where development
happens. When you mention an issue in another issue or pull
request, the issue's timeline reflects the cross-reference so that
you can keep track of related work. To indicate that work is in
progress, you can link an issue to a pull request.
22

Issue Tracking

Recommended

Recommended

More Related Content

Similar to Issue Tracking

Similar to Issue Tracking (20)

Recently uploaded

Recently uploaded (20)

Issue Tracking