10.46243/jst.2021.v6.i06.pp206-216 registered
Requirements engineering for e-Government services: A citizen-centric approach andcase study
Resolves to https://www.jst.org.in/index.php/pub/article/view/558
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2021.v6.i06.pp206-216
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 6044ba02402f6830…
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
Requirements engineering for e-Government services: A citizen-centric approach andcase study (PrincipalTitle)
Published 2021-12-29
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 06 · issue 06 · pages 206–216
Agents
- P. Kowmudi (author)
- B Swetha (author)
- B Narasimha Rao (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2021.v6.i06.pp206-216
Abstract
Throughout the last decade, user involvement in e-Government service design has been virtually non- existent. Over time, e-Government experts began to realize that these services would benefit from a citizen- centric requirements engineering approach which has led to a demand for such an approach for this particular field. This article presents a citizen-centric approach towards user requirements engineering for eGovernment services. It utilizes interviews and citizen walkthroughs of low-fidelity prototypes. A case study of a social support portal illustrates the approach and shows the need for repeated citizen inquiry, as the implementation of user requirements in low-fidelity prototype design is not always accepted by prospective end-users.
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.2021.v6.i06.pp206-216 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Requirements engineering for e-Government services: A citizen-centric approach andcase study (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: P. Kowmudi author: B Swetha author: B Narasimha Rao publisher: Longman Publishers published: 2021-12-29 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 06 · no. 06 · pp. 206–216 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) | 179 fields set · sha256 a0324dd3d7d1… |
| 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.
