%0 Conference Proceedings
%@holdercode {isadg {BR SPINPE} ibi 8JMKD3MGPCW/3DT298S}
%@usergroup administrator
%@usergroup chmendonca1977@yahoo.com.br
%@usergroup administrator
%3 paper.pdf
%J São José dos Campos
%I Instituto Nacional de Pesquisas Espaciais (INPE)
%B ISPE International Conference on Concurrent Engineering, 14 (CE 2007).
%9 Systems Engineering
%P 63-70
%X High integrated and complex systems are more and more scattered and common in people lives. Even without the exact feeling of this means, they hope for the best product. This desire implicate in system manufactures improve knowledgement and create solutions with more advanced technologies to satisfy consumers expectations. No much time ago, world saw the emergence of cell phones. In that time this technology was expansive and it was not so good, for instance, the coverage of signal was not so spread, batteries had no longer charge duration, displays only show the phone numbers and they have a nickname of "brick" because the excessive weight and size. Compare that with actual cell phones. Anyone can go to shop and buy a small one with voice recorder, integrated camera, internet access, expansible memories, among other features. It is only one brief and single example to demonstrate how the integrated system comes up in our lives and it could be replaced by video games, automobiles, domestics equipments, personal cares, computers, medicine among others. Manufacturers of high integrated systems need ensure that products will not cause problems to health or lives during them normal and abnormal operation and, of course, they must execute the desired work. The process to ensure correct implementation and development called System Verification. Verification have been done at the end of process development, but it have resulted in difficulties to manufacturers because is very expansive and hard to implement any required modifications at the end of development process. Thus, many manufactures have started verification process at begin of development, decreasing erroneous implementations. The usual way to advance verification tests is create mathematical models and simulate them in computers to verify normal and abnormal behavior. This is very useful during system development, but there are any problems that should be considerate: Which tests cases should be performed in models? Does the model have enough feature and functionalities implemented? Are the tests results as expected? A good approach to answer these questions is creating test cases procedures to know if models satisfy required necessities. But, how do create tests procedures without know completely the system under tests? At begin of development process, engineers write system description and system requirements thus, tests procedures should be done against these documents. This paper is intended to show an intuitive method possible to apply in any cases, using block diagrams, that assists generate test cases procedures, since when development starts, making relationship among system interfaces, subsystems and functions, enabling tests traceability and tests coverage analysis. In cases where manufacturer develops same kind of products, the block diagram will be easily reused to a new one, including or removing systems, subsystems and functions, adapting it to new features and project requirements.
%@session oral
%E Loureiro, Geilson,
%E Curran, Ricky,
%T The System Verification Breakdown Method
%@electronicmailaddress chmendonca1977@yahoo.com.br
%@format Print; CD-ROM; On-line.
%K verification, method, block diagram, coverage tests, requirements, reuse, test cases generation, system, sub-system, interfaces.
%@secondarytype CI
%8 2007, July 16-20
%@e-mailaddress chmendonca1977@yahoo.com.br
%@mark 1
%2 dpi.inpe.br/ce@80/2007/01.12.14.26.02
%@affiliation Instituto Nacional de Pesquisas Espaciais - INPE
%@subject Systems analysis, simulation and optimization
%4 dpi.inpe.br/ce@80/2007/01.12.14.26
%D 2007
%1 Instituto Nacional de Pesquisas Espaciais (INPE)
%S Proceedings
%A Mendonca, Cassio H.,
%C São José dos Campos
%@area ETES