Consultation by CATS is "practical consulting" leveraging experience gained from many prior investigations and development focusing on in-vehicle software development.We devise technological strategies through conversations with you and offer and support you for technical elements, development technology and management technology.
By ensuring C traceability, you can not only meet international standards like those of functional safety, but also manage the quality, cost and delivery schedule (QCD) of system development more effectively.Especially, at off-shore developments and maintenance phases, traceability is more important.
By ensuring and maintaining traceability, we "visualize" connection of information in the development process to make management easier.
It establishes traceability environment collaborating with Subversion and Trac/Redmine
Collaborating with modeling tools, ZIPC TERAS imports UML and state transition tables to realize traceability control.
By using the existing environment effectively, ALM a traceability environment with a tool chain is realized.
Are you looking for how to improve development efficiency and quality of development of many types of software?
Our consultants will help you establish a tool environment best suitable for you and define a process.
Software Product Line is a software development method to develop many types of software.By taking software to components and reusing them to configures each new product, cost and period of development are reduced.By applying Software Product Line, you can improve development efficiency.
To realize high quality in software development, it is required to associate different deliverables developed from multiple processes with each other to manage them.
In addition, requirements depending on products and common requirements are managed separately in Software Product Line.This management enables you to check linkage coverage among deliverables and analyze the impact at change to develop high quality products.
For Software Product Line, it is required to prepare process and organizations.
To manage these deliverables properly, you need the management method suitable for deliverables specific to the user.Also, it is required to prepare a definition of a document format enabling the management and guidelines for the developers.
To make Software Product Line successful, it is required to implement the implementation of the process and environment systematically.
To establish the effective tool environment contributing to SPL activities, it is required to start reviewing it from the stage of process definition and implementation plan.For long time, we have successfully provided solutions for SPL, including development of a modeling tool for SPL: "ZIPC Feature" and participation in development of a traceability control tool platform: "ZIPC TERAS".
The key to Software Product Line success is development plans. ZIPC Feature is a modeling tool for variation analysis, which is the most important analysis for development plans.ZIPC Feature with which you can create feature models through simple operation support development of Software Product Line.
Because there are so many items to check linkages among deliverables, manual operation is tough work.The management function for traceability among deliverables provided by ZIPC TERAS dramatically reduces repetitive reviews and impact scope confirmation work.Also, by collaborating with various tools including Microsoft Office , it makes registration of design information easy.ZIPC Feature collaborating with ZIPC TERAS provides traceability of feature models.
As division of labor and globalization of development proceed, documents needs are growing. However, we hear a lot of problems are due to documents.Also, development documents complying with international standards per industrial area are demanded to export products.This service improves the requirement definition process required for these standards and supports problem solving related to documents.
So far, when supporting customers' development, we have heard from them as below.
How about in your working place?In Japan, there are only a few opportunities to be educated in not only software development but also document creation for business. Therefore, documentation has a lower priority.
This service aims to improve development efficiency by creating proper documents without hesitation and eliminating communication errors through documents and reworking.Also, restoring "requirement" and "reason" unlikely to be communicated clearly in the high-context Japanese culture has the effect to clarify the judging criteria of validity of designs and tests.
As a secondary effect, you can realize traceability required these days only when you define the requirements property.Because you can prove that design (architecture), implementation and tests are completed based on the requirements, you can explain them with confidence to a third party.
This service consists of 3 improvement activities.
Firstly, we check the current development documents with you to clarify what has been done and what has not been done or needs improvement.At the time, we let you understand "mechanism of software development" and therefore we have acquired a favorable reputation especially from companies outsourcing software.Then, we define the required document referencing applicable standards depending on the industry of the product you are developing.If there is no reference standard, we use IEC29148 , which is an international standard for requirement engineering.
We analyze current documents, see if there is information required for the design and see your way of writing may be vulnerable to errors.
Referencing international standards as necessary, we define design methods and documents required for each process of software developmentAlso, we understand the mechanism of how communication errors occur outside of the process, and learn how to write required specifications preventing it.
This service features 3 tables: "USDM", "Organization Table for required specifications" and "State Transition Table" to be used depending on situations to prevent omissions in specifications. USDM focusing on "logical configuration", "Organization Table for required specifications" focusing on "sentence configuration" expressing structures, behaviors and performance requirements, and "State Transition Table" focusing on "states" of behavior complementing each other to help you find omissions.
Required specifications with USDM (Image)
Improved Comprehensiveness with Organization Table for Required Specifications
Service to Improve Upstream Documents plans depending on customers' situations and the representative flow is described as below.Firstly, we understand your current status and hold seminars and training for you.Then, after understanding the basics, we practice with an actual business theme accordingly and help you establish the skills.Anyway, do not hesitate to consult us about challenge you are facing.
If you have any question, inquiries, or support regarding instllation or other, please feel free to contact us.