10.46243/jst.2021.v6.i05.pp138-146 registered
Systematic Mapping Studies in Software Engineering
Resolves to https://www.jst.org.in/index.php/pub/article/view/925
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2021.v6.i05.pp138-146
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 39d422756f494cd4…
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
Systematic Mapping Studies in Software Engineering (PrincipalTitle · en)
Published 2021-10-01
Part of Journal of Science & Technology · ISSN 2456-5660 · pages 138
Agents
- CH Venkata Navi (author)
- P.Sandeep Reddy (author)
- G L N V Kartheek (author)
- G L N V Kartheek (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2021.v6.i05.pp138-146
Abstract · en
BACKGROUND: A software engineering systematic map is a defined method to build a classification scheme and structure a software engineering field of interest. The analysis of results focuses on frequencies of publications for categories within the scheme. Thereby, the coverage of the research field can be determined. Different facets of the scheme can also be combined to answer more specific research questions. OBJECTIVE: We describe how to conduct a systematic mapping study in software engineering and provide guidelines. We also compare systematic maps and systematic reviews to clarify how to chose between them. This comparison leads to a set of guidelines for systematic maps. METHOD: We have defined a systematic mapping process and applied it to complete a systematic mapping study. Furthermore, we compare systematic maps with systematic reviews by systematically analyzing existing systematic reviews. RESULTS: We describe a process for software engineering systematic mapping studies and compare it to systematic reviews. Based on this, guidelines for conducting systematic maps are defined. CONCLUSIONS: Systematic maps and reviews are different in terms of goals, breadth, validity issues and implications. Thus, they should be used complementarily and require different methods (e.g., for analysis).
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.i05.pp138-146 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Systematic Mapping Studies in Software Engineering (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: CH Venkata Navi author: P.Sandeep Reddy author: G L N V Kartheek author: G L N V Kartheek publisher: Longman Publishers published: 2021-10-01 part of: Journal of Science & Technology · ISSN 2456-5660 · pp. 138 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-11 | 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.
Recommended for a journal article and not in this record: the volume number · the issue number.
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 17 references; 14 carry a DOI.
| # | Reference | DOI | Held here |
|---|---|---|---|
| 1 | ref1 Bailey, J., Budgen, D., Turner, M., Kitchenham, B., Brereton, P. & Linkman, S. (2007), Evidence relating to object-oriented software design: A survey, in ‘Proc. of the 1st Int. Sy… | 10.1109/esem.2007.58 | not held here |
| 2 | ref2 Budgen, D., Kitchenham, B., Charters, S., Turner, M., Brereton, P. & Linjkman, S. (2007), Preliminary results of a study of the completeness and clarity of structured abstracts, i… | 10.14236/ewic/ease2007.7 | not held here |
| 3 | ref3 Davis, A. M., Tub´ıo, O´. D., Hickey, A. M., Juzgado, N. J. & Moreno, A. M. (2006), Effectiveness of requirements elicitation techniques: Empirical results derived from a systemat… | 10.1109/re.2006.17 | not held here |
| 4 | ref4 Dixon-Woods, M., Agarwal, S., Jones, D., Young, B. & Sutton, A. (2005), ‘Synthesising qualitative and quantitative evidence: a review of possible methods.’, Journal of Health Serv… | 10.1177/135581960501000110 | not held here |
| 5 | ref5 Glass, R. L., Vessey, I. & Ramesh, V. (2002), ‘Research in software engineering: an analysis of the literature’, Information & Software Technology 44(8), 491–506 | 10.1016/s0950-5849(02)00049-6 | not held here |
| 6 | ref6 Grimstad, S., Jørgensen, M. & Moløkken-Østvold, K. (2006), ‘Software effort estimation terminology: The tower of babel’, Information & Software Technology 48(4), 302–310 | 10.1016/j.infsof.2005.04.004 | not held here |
| 7 | ref7 Hannay, J. E., Sjøberg, D. I. K. & Dyba˚, T. (2007), ‘A systematic review of theory use in software engineering experiments’, IEEE Trans. Software Eng. 33(2), 87–107. Jørgensen, M… | 10.1109/tse.2007.12 | not held here |
| 8 | ref8 Kampenes, V. B., Dyba˚, T., Hannay, J. E. & Sjøberg, D. I. K. (2007), ‘Systematic review: A systematic review of effect size in software engineering experiments’, Information & So… | 10.1016/j.infsof.2007.02.015 | not held here |
| 10 | ref10 Kitchenham, B. A., Dyba, T. & Jorgensen, M. (2004), Evidence-based software engineering, in ‘Proc. of the 26th Int. Conf. on Software Engineering (ICSE 2006)’, IEEE Computer Socie… | 10.1109/icse.2004.1317449 | not held here |
| 11 | ref11 Kitchenham, B. A., Mendes, E. & Travassos, G. H. (2007), ‘Cross versus within-company cost estimation studies: A systematic review’, IEEE Trans. Software Eng. 33(5), 316–329 | 10.1109/tse.2007.1001 | not held here |
| 13 | ref13 MacDonell, S. G. & Shepperd, M. J. (2007), Comparing local and global software effort estimation models-reflections on a systematic review, in ‘Proc. of the 1st Int. Symp. on Empi… | 10.1109/esem.2007.45 | not held here |
| 14 | ref14 Mendes, E. (2005), A systematic review of web engineering research, in ‘Proc. of the Int. Symp. on Empirical Software Engineering (ISESE 2005)’, pp. 498–507 | 10.1109/isese.2005.1541857 | not held here |
| 15 | ref15 Mujtaba, S., Petersen, K., Feldt, R. & Mattsson, M. (2008), Software product line variability: A systematic mapping study, in ‘submission’. Sjøberg, D. I. K., Hannay, J. E., Hanse… | 10.1109/tse.2005.97 | not held here |
| 17 | ref17 Wieringa, R., Maiden, N. A. M., Mead, N. R. & Rolland, C. (2006), ‘Requirements engineering paper classification and evaluation criteria: a proposal and a discussion’, Requir. Eng… | 10.1007/s00766-005-0021-6 | not held here |
Relations
The record states no relation, and no record held here states one with this DOI.
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.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 111 fields set · sha256 0f0de173112d… |
| 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.
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.
| When | What changed | Crossref | Fingerprint |
|---|---|---|---|
| 11 Sep 2026, 16:46 | Address updated from https://www.jst.org.in/index.php/pub/article/view/925/852 to https://www.jst.org.in/index.php/pub/article/view/925 | ● accepted by Crossref | 726a6727ed10… |
| 13 Sep 2026, 01:40 | Read back: the DOI resolves to the new address | ● confirmed | e8ece01015eb… |
| 15 Oct 2026, 15:30 | Metadata completed abstract (192 words) · licence | ● accepted by Crossref | a76aa1ed7f0e… |
| 15 Oct 2026, 16:19 | Read back: Crossref's record shows it | ● confirmed | 40ce75557064… |
4 entries · the last fingerprint 40ce75557064cdefdaa8a2f1700e3ca6b4d383f0a83877fb75097a943f9932eb · the history as JSON, each entry with the fingerprint before it, to check them yourself.



