eSpline's Managing VC
improves the process...
eSpline added
governance to the VC & IPC change process that improves quality and productivity with a combination
of software tools and partner software running on an
eSpline hosted server or on a server behind your firewall.
It is a long
process and you go through many of these manually. Governance
can begin here:
(1)
Managing VC provides multiple ways to
Extract
a product model to an SaaS application
(2)
You make changes to a copied VC or IPC product model
(3)
You direct Managing VC to Extract the
changed VC product model or IPC Kb
(4) Now, there are two [2] versions of a VC or IPC
product model [original and changed]
(5)
View
the model characteristics, pre-conditions, materials,
dependency nets, long text, etc. in an easy
to read HTML from or create a PDF with active links for easy
navigation of the model
(6)
Compare
the two models and see the differences
highlighted in color, in seconds
(7) Managing VC recognizes changes,
creates a test case and
sends the test case to
ConfigScan (Automated VC
Testing solution)
(8) You click on the change and to make a comment or a request and send a
message to your other VC Teams members or tester.
(9) Managing VC sends an email with the message/comment for review and
answer with a comment
(10) You may create additional, reusable test cases to automatically test your
changes
(11) Then, you automatically
test
the changed model to make sure there are no conflicts
resulting
(12) Repeat until the model behavior is stable and results are
correct and documented
(13) ConfigScan informs Managing VC
with a notification
message that the test cases passed
(14) You review the changes and
formally
approve the changes
with a click of the mouse
(15) You, direct an automatic
move
or upload of the changed
model to a target SAP instance
(16) Create a Engineering Change Notice for the changes
approved
(17)
Then, you have Managing VC
document
and
archive
the model by including the
Model View
PDF generated report,
the generated test cases, the new VC model, original VC model,
the
Managing VC log files and
your original specifications. ..\..\
So, now you have planned
the change, made the change, created test cases, tested the
changes, compared the changes, reviewed the changes, approved
and moved them to another instance. This is a much
improved governance process for managing your SAP models.
You now have a history of
the changes and tests. You now have a repository of the
changes with the original and new VC models and you have done it
in nearly half the time as the manual process. This is
improved productivity.
Except for making the
model changes, the change process has been improved and automated.
Your model is thoroughly tested and the Project Manager has seen
the test results, the changes and approved for production.
