10.46243/jstj.2017.v2.i1.135 registered
Significance of Software Layered Technology on Size of Projects
Resolves to https://www.jst.org.in/index.php/pub/article/view/135
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jstj.2017.v2.i1.135
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 8ddd0f33bb9b0a49…
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
Significance of Software Layered Technology on Size of Projects (PrincipalTitle · en)
Published 2017-01-12
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 02 · issue 01 · pages 46–58
Agents
- Jogannagari Malla Reddy (author)
- S.V.A.V. Prasad (author)
- B.V. Ramana Murthy (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jstj.2017.v2.i1.135
Abstract · en
The objective of the software engineering is committed to build software projects within the budget, time and required quality. Software engineering is a layered paradigm comprised of process, methods, tools and quality focus as bedrock to develop the product. Software firms build software projects of varying sizes constrained on resources, time and functional requirement. Impact of software engineering layered technology may vary according to the size of the projects during their development. Quantitative evaluation of layer significance on size of the software project could be categorized as a complex task because it involves a collective decision on multiple criteria. Analytic Hierarchy Process(AHP) provides an effective quantitative approach for finding the significance of software layered technology on size of the projects. This paper presents the estimations through quantitative approach on real time data collected from several software firms. These findings help for a better project management with respect to the cost, time and resources during building a softwareproject.
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/jstj.2017.v2.i1.135 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Significance of Software Layered Technology on Size of Projects (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Jogannagari Malla Reddy author: S.V.A.V. Prasad author: B.V. Ramana Murthy publisher: Longman Publishers published: 2017-01-12 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 02 · no. 01 · pp. 46–58 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-07 | 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
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 20 references; 7 carry a DOI.
| # | Reference | DOI | Held here |
|---|---|---|---|
| 3 | ref3 Sadia Rehman et al, “SWOT Analysis of Software Quality Metrics for Global Software Development: A Systematic Literature Review Protocol”, IOSR Journal of Computer Engineering, Vol… | 10.9790/0661-0210107 | not held here |
| 7 | ref7 M.S.Rawat, A. Mittal, S.K. Debey, “Survey on Impact of Software Metrics on Software Quality”, Vol.3, International Journal of Advancement Computer Science and Applications, 2012 | 10.14569/ijacsa.2012.030121 | not held here |
| 9 | ref9 Saaty, T.L (2000), “The Analytic Hierarchy Process”, Mc Graw-Hill International, New York, NY, 2000 | 10.13033/isahp.y1999.038 | not held here |
| 11 | ref11 Satty, T.L,“Scaling method for priorities in hierarchical structures”, Journal of Mathematical Psychology, pp 234–281, 1977 | 10.1016/0022-2496(77)90033-5 | not held here |
| 12 | ref12 Saaty, T.L: “ How to Make a Decision : The Analytic Hierarchical Process”, European Journal of Operational Research, Vol 48, pp 9–26, 1990 | 10.1016/0377-2217(90)90057-i | not held here |
| 15 | ref15 Norita Ahmad, “ Software Project Management Tools : Making a Practical Decision Using AHP”, Proceedings of the Annual IEEE/NASA Software Engineering Workshop, IEEE Xplore, 2006 | 10.1109/sew.2006.30 | not held here |
| 20 | ref20 Singh Yogesh & Pradeep Bhatia, “Module Weakness-New Measures”, ACM SIGSOFT Software Engineering Notes, 81, July,1998 | 10.1145/290249.290270 | 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) | 109 fields set · sha256 41a698852cbd… |
| 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, 05:24 | Address updated from https://www.jst.org.in/index.php/pub/article/view/135/117 to https://www.jst.org.in/index.php/pub/article/view/135 | ● accepted by Crossref | fb0b9643daeb… |
| 13 Sep 2026, 01:41 | Read back: the DOI resolves to the new address | ● confirmed | 64ed6b56591f… |
| 15 Oct 2026, 15:30 | Metadata completed abstract (158 words) · licence | ● accepted by Crossref | 48516ac29394… |
| 15 Oct 2026, 16:16 | Read back: Crossref's record shows it | ● confirmed | a82f7fb91ad8… |
4 entries · the last fingerprint a82f7fb91ad8112d65ddc32060355d9091442b68e1640da83f1a4e6379face13 · the history as JSON, each entry with the fingerprint before it, to check them yourself.



