Skip to content
Smart Scholars🛡 Scholar Shield🏛 Research Integrity Desk🧩 Portfolio Console📰 Journals🔧 DOI MembersTools🔎 Journal AuditGI GetIndexedDr DOI Doctor

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)

Also as schema.org JSON-LD · Turtle · RDF/XML · DataCite XML · Crossref UNIXREF · Crossref UNIXSD — the formats of the DOI content-negotiation service, from this record (which carries what).

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 · en)

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 · en

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.

Licence https://creativecommons.org/licenses/by/4.0/

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.

ElementValueIn the record
DOI Name
DOI name
10.46243/jst.2021.v6.i06.pp206-216doi
Referent Type
referentType
Creationreferent
Referent Sub-Type
referentSubType
JournalArticle — an article in a journaltype
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 DOIidentifiers, relations (IsSameAs)
Registration Authority
registrationAuthorityCode
Crossref — issued by Crossref (member 25296); held here as a copyrecord.source_agency (our code, ra_doi_name, for names issued here once appointed)
Created Date
issueDate
2026-09-08record.registered (when the DOI name was first registered)
relatedIdentifiersnone needed — the descriptive metadata is in this recordcontainer, 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

Cited by — in this registry

No record held in this registry cites this DOI.

Counts only records held in this registry; a citation from a work held elsewhere is not seen here. The list as JSON

References with DOIs

The record lists 41 references; 35 carry a DOI.

#ReferenceDOIHeld here
2ref2 Alpert, S. R., & Vergo, J. G. (2007). User-centered evaluation of personalized web sites: What's unique? In P. Zaphiris, & S. Kurniawan (Eds.), Human computer interaction. Researc…10.4018/978-1-59904-246-6.ch012not held here
3ref3 Ambrosini, V., & Bowman, C. (2001). Tacit knowledge: Some suggestions for operationalization. Journal of management studies, 38(6), 811−82910.1111/1467-6486.00260not held here
4ref4 Becker, S. A. (2004). e-Government visual accessibility for older adult users. Social science computer review, 22(1), 11−23. Benchmark perzonalization of governmental eServices fo…10.1177/0894439303259876not held here
5ref5 Benyon-Davies, P., Tudhope, D., & Mackay, H. (1999). Information systems prototyping in practice. Journal of information technology, 14(1), 107−12010.1177/026839629901400109not held here
6ref6 Coble, J. M., Karat, J., & Kahn, M. G. (1997). Maintaining a focus on user requirements throughout the development of clinical workstation software. Paper presented at CHI'97, Atl…10.1145/258549.258698not held here
7ref7 Cooper, A. (1999). The inmates are running the asylum. Why high-tech products drive us crazy and how to restore the sanity. Indianapolis: SAMS10.1007/978-3-322-99786-9_1not held here
8ref8 Damodaran, L. (1996). User involvement in the systems design process—A practical guide for users. Behaviour and information technology, 15(6), 363−37710.1080/014492996120049not held here
9ref9 Davis, B. G. (1982). Strategies for information requirements determination. IBM systems journal, 21(1), 4−3010.1147/sj.211.0004not held here
10ref10 Flak, L. S., Moe, C. E., & Sæbø, Ø. (2003). On the evolution of e-Government: The user imperative. In R. Traunmüller (Ed.), EGOV 2003, LNCS, vol. 2739 (pp. 139−142). Heidelberg: S…10.1007/10929179_25not held here
11ref11 Gould, J. D., & Lewis, C. (1985). Designing for usability: Key principles and what designers think. Communications of the ACM, 28(3), 300−31110.1145/3166.3170not held here
12ref12 Grady, H. M. (2000). Web site design: A case study in usability testing using paper prototypes. Paper presented at the IEEE Professional Communication Conference, Cambridge, USA10.1109/ipcc.2000.887259not held here
13ref13 Gremler, D. D. (2004). The critical incident technique in service research. Journal of service research, 7(1), 65−8910.1177/1094670504266138not held here
15ref15 Hertzum, M., & Jacobsen, N. E. (2001). The evaluator effect: A chilling fact about usability evaluation methods. International Journal of Human–Computer Interaction, 13(4), 421−44310.1207/s15327590ijhc1304_05not held here
16ref16 Irani, Z., & Love, P. E. D. (2001). The propagation of technology management taxonomies for evaluating investments in information systems. Journal of management information system…10.1080/07421222.2000.11045650not held here
17ref17 Irani, Z., Love, P. E. D., Elliman, T., Jones, S., & Themistocleous, M. (2005). Evaluating e-Government: Learning from the experiences of two UK local authorities. Information Sys…10.1111/j.1365-2575.2005.00186.xnot held here
18ref18 Jameson, A. (2007). Adaptive interfaces and agents. In J. A. Jacko, & A. Sears (Eds.), Human–computer interaction handbook (pp. 433−458). 2nd ed. Mahwah: Erlbaum10.1201/9781410615862.ch22not held here
20ref20 Karat, C. (1994). A business case approach to usability cost justification. In R. G. Bias, & D. J. Mayhew (Eds.), Cost-justifying usability (pp. 45−70). New York: Morgan Kaufmann10.1016/b978-012095811-5/50004-3not held here
21ref21 Kinzie, M. B., Cohn, W. F., Julian, M. F., & Knaus, W. A. (2002). A user-centered model for web site design: Needs assessment, user interface design, and rapid prototyping. Journa…10.1197/jamia.m0822not held here
22ref22 Klaassen, R., Karreman, J., & Van der Geest, T. (2006). Designing government portal navigation around citizens' needs. In M. A. Wimmer, H. J. Scholl, A. Grönlund, & K. V. Andersen…10.1007/11823100_15not held here
23ref23 Krenner, J. (2002). Reflections on the requirements gathering in an one-stop government project. In R. Traunmüller, & K. Lenk (Eds.), EGOV 2002, LNCS, vol. 2456 (pp. 124−128). Hei…10.1007/978-3-540-46138-8_19not held here
24ref24 Kujala, S. (2003). User involvement: A review of the benefits and challenges. Behaviour and information technology, 22(1), 1−1610.1080/01449290301782not held here
26ref26 Lines, L., Ikechi, O., & Hone, K. S. (2007). Accessing e-Government services: Design requirements for the older user. In C. Stephanidis (Ed.), Universal access in HCI, LNCS, vol. …10.1007/978-3-540-73283-9_101not held here
27ref27 Maguire, M. (2001). Methods to support human-centred design. International Journal of Human–Computer studies, 55(4), 587−63410.1006/ijhc.2001.0503not held here
28ref28 Mao, J., Vredenburg, K., Smith, P. W., & Carey, T. (2005). The state of user-centered design practice. Communications of the ACM, 48(3), 105−10910.1145/1047671.1047677not held here
29ref29 McGraw, K. L., & Harbison, K. (1997). User-centered requirements: The scenario-based engineering process. Mahwah: Lawrence Erlbaum Associates10.1201/9781003064138not held here
30ref30 Oostveen, A., & Van de besselaar, P. (2004). From small scale to large scale user participation: A case study of participatory design in e-Government systems. Paper presented at t…10.2139/ssrn.1432508not held here
31ref31 Patton, M. Q. (2002). Qualitative research and evaluation methods (3rd ed.). Thousand Oaks: Sage Publications10.1177/10928102005003006not held here
32ref32 Pieterson, W., Ebbers, W., & Van Dijk, J. (2007). Personalization in the public sector. An inventory of organizational and user obstacles towards personalization of electronic ser…10.1016/j.giq.2005.12.001not held here
34ref34 Rudd, J., Stern, K., & Isensee, S. (1996). Low vs. high-fidelity prototyping debate. Interactions, 3(1), 76−8510.1145/223500.223514not held here
35ref35 Saiedian, H., & Dale, R. (2000). Requirements engineering: Making the connection between the software developer and customer. Information and Software Technology, 42(6), 419−42810.1016/s0950-5849(99)00101-9not held here
36ref36 Sandberg, K. W., & Pan, Y. (2007). The role of human factors in design and implementation of electronic public information systems. In D. Harris (Ed.), Engineering psychology and …10.1007/978-3-540-73331-7_18not held here
38ref38 Soufi, B., & Maguire, M. (2007). Achieving Usability within e-Government web sites illustrated by a case study evaluation. In M. J. Smith, & G. Salvendy (Eds.), Human interface, p…10.1007/978-3-540-73354-6_85not held here
39ref39 Sutcliffe, A. (1996). A conceptual framework for requirements engineering. Requirements engineering, 1(3), 170−18910.1007/bf01236426not held here
40ref40 Sutcliffe, A. (1997). A technique combination approach to requirements engineering. Paper presented at the 3rd IEEE International Symposium on Requirements Engineering, Annap olis…10.1109/isre.1997.566843not held here
41ref41 Wang, L., Bretschneider, S., & Gant, J., (2005). Evaluating web-based e-Government services with a citizen-centric approach. Paper presented at the 38th Hawaii International10.1109/hicss.2005.252not held here

The references as JSON

Relations

The record states no relation, and no record held here states one with this DOI.

The relations as JSON

Funding

The record names no funder.

Each funder's page lists every work held here that names it. ROR IDs open at ror.org; Funder Registry IDs resolve at doi.org.

History — the ledger

Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.

#WhenWhatByChanges
129 Sep 2026, 10:00 PMregister
registered at Crossref; record read from api.crossref.org
Administrator (admin) 179 fields set · sha256 a0324dd3d7d1…
229 Sep 2026, 11:59 PMupdate
record re-read from api.crossref.org
Administrator (admin)
container.titles.0.value: Journal of Science & Technology → Journal of Science & Technology

Machine-readable: the history as JSON, with the full record after each change.

Changes made at Crossref through DOI Doctor

Every deposit Smart Scholars' DOI Doctor made for this DOI, oldest first, with Crossref's own answer. Each fingerprint is the SHA-256 of its entry and of the fingerprint before it, so a change to any earlier entry changes every fingerprint after it.

WhenWhat changedCrossrefFingerprint
09 Sep 2026, 12:50Licence added
https://creativecommons.org/licenses/by/4.0/
● accepted by Crossrefdf07c233b49f…
11 Sep 2026, 05:18Address updated
from https://www.jst.org.in/index.php/pub/article/view/558/499 to https://www.jst.org.in/index.php/pub/article/view/558
● accepted by Crossrefe2c77df09c84…
13 Sep 2026, 01:40Read back: the DOI resolves to the new address● confirmed3928d048f124…
21 Sep 2026, 00:54Metadata completed
publication date
● waiting for Crossref's answer85174017d216…
21 Sep 2026, 01:46Read back: Crossref's record shows it● confirmed65242f0fa4ee…

5 entries · the last fingerprint 65242f0fa4ee815f80c4cee54cf6c5c4321c42f53f8109d5f70d05b17bce9f02 · the history as JSON, each entry with the fingerprint before it, to check them yourself.

Share this page

Share this page

Ask AI about this page

Everything Smart Scholars runs

Nine sites, one account. A journal starts at the audit; an author starts at Scholar Shield.

What we do: DOIs registered from what a journal already has · Crossref records completed — references, abstracts, licences, ORCID iDs, affiliations and ROR IDs, funding · DOIs that resolve · articles preserved · journals rated on the public record · see everything we do →

Book a free call

For journals & publishers

Start with the audit — ₹4,999 per journal, and the gate to everything else.

DOI care

Every service on one journal profile — each previews first and acts only on your approval.

  • DOI Doctor — check & repairevery DOI tested at doi.org and Crossref; dead links, abstracts, licences, ORCIDs
  • Smart Deposita new DOI from your PDF, Word file, article page, JATS XML or spreadsheet — every value shown with its source, deposited once you confirm it
  • DOI census (Excel)site against Crossref, both directions, with a copy-paste fix per article
  • Backfile DOIsDOIs for older articles that never had one — no per-DOI fee of ours
  • DOIs for conference proceedingsthe conference, the volume and every paper — registered in the organiser's own name
  • Scopus indexing guidethe minimum criteria, the 14 CSAB criteria and how a title is suggested — from Elsevier's own page
  • Embase indexing guidewhat Embase asks of a biomedical journal and how to suggest it
  • Write DOIs into OJSthe verified DOIs pushed onto your article pages through your own API
  • Silent-failure monitorweekly checks of site, OAI-PMH, Scholar tags, ISSN, preservation, hijack lists
  • Journal Radarevery journal, every day: SSL, DNS, redirects, robots.txt, OJS, DOIs, Crossref metadata, broken links — what broke since yesterday first
  • Verified metrics & badgesa public, dated, source-linked metrics page and a "cited by" badge
  • Quality dossier (PDF)one PDF for universities, authors and reviewers
  • Author citation enginethe citation steps emailed to each author from the journal's own mailbox
  • JATS XMLmachine-readable JATS per article
  • Duplicate articlesthe same paper published twice — you choose which copy stays

For authors & researchers

Free to use. Nothing you check is shared with the journal.

For institutions, sponsors & DOI operators

Smart Scholars

Mon–Sat, 10:00–19:00 IST. The Ask AI button on every page answers about our services at any hour.

News

Policies

What we can register a DOI for

20 kinds of record, one account, one place. Every one gets a DOI that resolves, metadata that indexes read, and a record that stays correct afterwards.

Journals

  • Journal articles
  • Journal titles
  • Pending publications
  • Peer reviews
  • Preprints & posted content

Books & conferences

  • Books
  • Book chapters
  • Book series
  • Book sets
  • Conference proceedings
  • Proceedings series
  • Conference papers

Other research output

  • Theses & dissertations
  • Reports & working papers
  • Report series
  • Standards
  • Databases
  • Datasets
  • Figures, tables & supplements

Funding

  • Grants & funding awards

Elsewhere

The same company, in the places our publishers already read.
Add Smart Scholars as a preferred source on GoogleSee more of our newsroom in Google’s Top Stories.
Smart Scholars · Every service on one pageNewsroom posts CC BY 4.0 · DOI metadata CC0 · everything else ©Data from OpenAlex (openalex.org), CC0 · Crossref · ISSN Portal · DOAJContact
WhatsApp