Event Details

View All Recorded Events
Date Event Type 場所 Action
Oct 19, 2017

Abstract

 

Late discovery of requirement errors in the project cycle are very expensive to fix. Requirement changes are common and they are expected to happen on any given project. Microsoft® Office™ tools such as Word and Excel do not facilitate the required environment for managing constantly changing requirements because they impede collaboration, do not provide requirement versions comparison and lack the required traceability automation and precision.

 

During this webinar, we will present and analyze the limitations of Office tools that disqualify them from the professional requirements management process. At the same time we will show you how these limitations are addressed in Spec-TRACER and how to use the professional Requirements Management tool to help streamline your organization’s processes and get better production in shorter time.

 

Agenda

 

  • Why Requirements Management is so important for FPGA projects?
  • Limitations of Microsoft® Word in Requirements Engineering
  • How Microsoft® Word limitations are addressed in Spec-TRACER™?
  • Spec-TRACER™ demo
  • Conclusion
  • Q&A

Presenter Bio

Janusz Kitel is a Requirements Management Specialist at Aldec. He is responsible for the Spec-TRACER product line. Janusz has 5 years of experience in requirements engineering and over 10 years of experience in product quality assurance. Janusz received his M.S. in Electronics and Telecommunication from Silesian University of Technology and increased his knowledge about software engineering from complementary studies at AGH University of Science and Technology (Poland). His practical engineering experience includes areas in functional verification, DO-254 compliance and software development.

ウェブセミナー More Info
Ask Us a Question
x

Ask Us a Question

x
Captcha ImageReload Captcha
Incorrect data entered.
Thank you! Your question has been submitted. Please allow 1-3 business days for someone to respond to your question.
Internal error occurred. Your question was not submitted. Please contact us using Feedback form.