CoChat
Sign Up
Cited by 4Software Engineering Techniques and PracticesAdvanced Software Engineering MethodologiesSafety Systems Engineering in Autonomy

The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.

A Model for Understanding Project Requirements based on CMMI Specifications

Odeh, Ammar, El-Hassan, Ammar, Keshta, Ismail, AlHajahjeh, Tareq·2021·2021 International Conference on Engineering and Emerging Technologies (ICEET)
DOI 10.1109/iceet53442.2021.9659625
Open this paper in CoChat — free account

Abstract

The main objective is to make sure that all the stakeholders understand the issues in the development of software. Knowing the needs ensures the success of the project. CAMI Level 2, therefore, helps organizations improve processes of software by providing them with important special practices to improve their software. Level 2 (in other words, SP 1.1 “understand requirements”). This practice helps developers to understand the problem and the needs of the domain in full. In this paper, we have visited three companies and conducted three detailed interviews. We have also developed a model of SP 1.1 by taking advantage of the different opinions and experiences of practices on the implementation of SP 1.1. This model comprises four key stages: preparation, analysis, validation, and updating. It will provide practitioners with key advice on how to implement SP 1.1 effectively.

Overview

Integrity signals

Registry

Crossref · 10.1109/iceet53442.2021.9659625

Cites

1 of 1 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Flagged first, then by citations

Show all 1 references

Research works printed but not linked: 30

  1. ammar, 2020, Efficient Detection of Phishing Websites Using Multilayer Perceptron, 22
  2. clarke, 2013, An empirical examination of the extent of software process improvement in software SMEs, Journal of Software: Evolution and Process, 25, 981
  3. 10.1109/MS.2017.4541041 · DOI
  4. 10.1109/MS.2007.12 · DOI
  5. chrissis, 2006, CMMI® Guidelines for Process Integration and Product Improvement
  6. 10.1109/SITA.2015.7358391 · DOI
  7. 10.17706/jsw.14.11.519-529 · DOI
  8. 10.1109/ACCESS.2017.2764490 · DOI
  9. 10.1109/ACCESS.2018.2859249 · DOI
  10. keshta, 2019, A model for defining project lifecyc1e phases: Implementation of CMMI level 2 specific practice, Journal of King Saud University-Comp and Info Sciences
  11. 10.1109/ICCSIT.2010.5563968 · DOI
  12. 10.1023/A:1009848320066 · DOI
  13. 10.1002/spip.409 · DOI
  14. 10.1049/iet-sen.2019.0180 · DOI
  15. 10.1016/j.infsof.2009.03.001 · DOI
  16. 10.1016/j.jss.2006.09.008 · DOI
  17. 10.3844/jcssp.2020.1346.1354 · DOI
  18. sanchez-gordon, 0, Mapping between CMMI-DEV vl.3 and ISO/IEC 90003:2014, 2019 International Conference on Information Systems and Software Technologies (ICI2ST), 134
  19. wu, 2005, A survey of CMM/CMMI implementation in China, Software Process Workshop, 507
  20. 10.1007/978-3-540-73460-4_13 · DOI
  21. mcallister, 2006, Requirements Determination of Information Systems User and Developer Perceptions of Factors Contributing to Misunderstandings
  22. al-tarawneh, 2013, Software development process improvement framework (SDPIF) for small software development firms (SSDFs), Int J Comput Sci Issues, 10, 475
  23. 10.1007/BF00127446 · DOI
  24. sommerville, 2011, Software Engineering
  25. persse, 2007, Project management success with CMMI seven CMMI process areas
  26. saqib, 2013, Understanding requirement engineering practices: An empirical study of the Pakistani software industry, Knowledge-Based Processes in Software Development
  27. 10.1007/978-0-85729-172-1 · DOI
  28. moorthy, 2013, CMMI Implementation Guide A Practitioner’s Perspective
  29. 2010, SEI'CMMI for development version 1 3 CMMI-DEV V1 3
  30. krippendorf, 1980, Content Analysis An Introduction to Its' Methdology

Cited by

Sorted by citations

See all 4

Metadata

Authors
Odeh, A., El-Hassan, A., Keshta, I., & AlHajahjeh, T.
Affiliations
  • Princess Sumaya University for Technology (JO)
  • Almaarefa University (SA)
ORCID
Venue
2021 International Conference on Engineering and Emerging Technologies (ICEET)
Publisher
IEEE
Published
2021-10-27
Volume
25
Pages
1-6
DOI
10.1109/iceet53442.2021.9659625
OpenAlex
W4206081671
Cited by
4
References
1
Citations by year
2023: 2 · 2022: 2
FWCI
0.67
Type
conference paper
Language
en
Open access
closed
Licence
Locations
International Conference on Engineering and Emerging Technologies (ICEET) (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
  • Physical Sciences › Engineering › Safety, Risk, Reliability and Quality › Safety Systems Engineering in Autonomy
Keywords
CMMI level 2, stakeholder needs, software process improvement, requirements validation, requirements analysis

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review