10.46243/jst.2020.v5.i6.pp159-164 registered
Implementation of Transient Current Testing for Faults in SRAM
Resolves to https://www.jst.org.in/index.php/pub/article/view/509
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2020.v5.i6.pp159-164
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 676199996f6ea9b7…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Implementation of Transient Current Testing for Faults in SRAM (PrincipalTitle)
Published 2020
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 05 · issue 06 · pages 159–164
Agents
- G.Usharani (author)
- J.Sneha Latha (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2020.v5.i6.pp159-164
Abstract
In recent years, as memory devices have risen in popularity, a higher quantity of memory has been packed into each chip, and fierce market competition has upped the quality standards that are expected of the memories that are produced. The notion that failure analysis and device testing methodologies are becoming increasingly important as a result of the rising demand for dependability has been emphasised repeatedly. It has been more popular to study and research memory devices in recent years, particularly in the context of novel failure models, fault detection methodologies, and new memory architectures that have all been developed and implemented. A direct effect of this experience is that the March test is now frequently used to identify and avoid similar problems from occurring in the future. The organisation believes that some vulnerabilities in SRAM cells may go undetected during the normal March testing. In order to determine whether or not there are defects in the CMOS SRAM, a time-consuming procedure has been implemented. It is as a result of this decision that the most recent testing process is selected for usage. As part of this research effort, IDDT is being used to test for faults and issues in CMOS SRAM cells, and it is also being used to test for flaws and issues in CMOS SRAM cells as part of a separate study of the same name. In either case, a transient current pulse generated during a transition write operation or a transition read operation may be monitored for system failures, allowing them to be discovered and remedied. For the purpose of detecting and measuring the transient current pulse, it is required to design a circuit for monitoring current. SRAM, memory testing, the March algorithm, the IDDT, and the current sensor circuit are just a few of the terms that appear in this document.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2020.v5.i6.pp159-164 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Implementation of Transient Current Testing for Faults in SRAM (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: G.Usharani author: J.Sneha Latha publisher: Longman Publishers published: 2020 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 05 · no. 06 · pp. 159–164 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2026-09-08 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 98 fields set · sha256 bd631d544c4c… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
