International Journal of

ADVANCED AND APPLIED SCIENCES

EISSN: 2313-3724, Print ISSN: 2313-626X

Frequency: 12
line decor
  
line decor

 Volume 8, Issue 11 (November 2021), Pages: 104-118

----------------------------------------------

 Original Research Paper

 Title: Constructing a software requirements specification and design for electronic IT news magazine system

 Author(s): Ra’Fat Al-Msie’deen 1, *, Anas H. Blasi 1, Mohammed A. Alsuwaiket 2

 Affiliation(s):

 1Department of Computer Information Systems, Mutah University, Karak, Jordan
 2Department of Computer Science and Engineering Technology, Hafar Batin University, Hafar Al-Batin, Saudi Arabia

  Full Text - PDF          XML

 * Corresponding Author. 

  Corresponding author's ORCID profile: https://orcid.org/0000-0002-9559-2293

 Digital Object Identifier: 

 https://doi.org/10.21833/ijaas.2021.11.014

 Abstract:

Requirements engineering process intends to obtain software services and constraints. This process is essential to meet the customer's needs and expectations. This process includes three main activities in general. These are detecting requirements by interacting with software stakeholders, transferring these requirements into a standard document, and examining that the requirements really define the software that the client needs. Functional requirements are services that the software should deliver to the end-user. In addition, functional requirements describe how the software should respond to specific inputs, and how the software should behave in certain circumstances. This paper aims to develop a software requirements specification document of the electronic IT news magazine system. The electronic magazine provides users to post and view up-to-date IT news. Still, there is a lack in the literature of comprehensive studies about the construction of the electronic magazine software specification and design in conformance with the contemporary software development processes. Moreover, there is a need for a suitable research framework to support the requirements engineering process. The novelty of this paper is the construction of software specification and design of the electronic magazine by following the Al-Msie'deen research framework. All the documents of software requirements specification and design have been constructed to conform to the agile usage-centered design technique and the proposed research framework. A requirements specification and design are suggested and followed for the construction of the electronic magazine software. This study proved that involving users extensively in the process of software requirements specification and design will lead to the creation of dependable and acceptable software systems. 

 © 2021 The Authors. Published by IASE.

 This is an open access article under the CC BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/).

 Keywords: Software engineering, Requirements engineering, Requirements specification, Agile software development, Usage-centered design, Interactive multimedia magazine

 Article History: Received 15 June 2021, Received in revised form 29 August 2021, Accepted 5 September 2021

 Acknowledgment 

No Acknowledgment.

 Compliance with ethical standards

 Conflict of interest: The author(s) declared no potential conflicts of interest with respect to the research, authorship, and/or publication of this article.

 Citation:

 Al-Msie’deen R, Blasi AH, and Alsuwaiket MA (2021). Constructing a software requirements specification and design for electronic IT news magazine system. International Journal of Advanced and Applied Sciences, 8(11): 104-118

 Permanent Link to this page

 Figures

 Fig. 1 Fig. 2 Fig. 3 Fig. 4 Fig. 5 Fig. 6 Fig. 7 Fig. 8 Fig. 9

 Tables

 Table 1 Table 2 Table 3 Table 4

----------------------------------------------    

 References (41)

  1. Alfrijat AM and Al-Msie’deen R (2009). A requirement model of local news WAP/WEB application for rural community. Advances in Computer Science and Engineering, 4(1): 37–53.   [Google Scholar]
  2. Al-Msie’deen R (2014). A requirement model of local news application for rural communities: A new model for rural news. LAP LAMBERT Academic Publishing, Sunnyvale, USA.   [Google Scholar]
  3. Al-Msie’deen R (2015). Visualizing object-oriented software for understanding and documentation. International Journal of Computer Science and Information Security, 13(5): 18–27.   [Google Scholar]
  4. Al-Msie’deen R (2018). Automatic labeling of the object-oriented source code: The lotus approach. Science International-Lahore, 30(1): 45–48.   [Google Scholar]
  5. Al-Msie’deen R (2019a). Object-oriented software documentation. 1st Edition, Lap Lambert Academic Publishing, Sunnyvale, USA. https://doi.org/10.17485/ijst/2018/v11i8/121148   [Google Scholar]
  6. Al-Msie’deen R (2019b). Tag clouds for software documents visualization. International Journal on Informatics Visualization, 3(4): 361–364. https://doi.org/10.30630/joiv.3.4.285   [Google Scholar]
  7. Al-Msie’deen R (2019c). Tag clouds for the object-oriented source code visualization. Engineering, Technology and Applied Science Research, 9(3):4243–4248. https://doi.org/10.48084/etasr.2706   [Google Scholar]
  8. Al-Msie’deen R and Blasi A (2018). The impact of the object-oriented software evolution on software metrics: The iris approach. Indian Journal of Science and Technology, 11(8): 1–8. https://doi.org/10.17485/ijst/2018/v11i8/121148   [Google Scholar]
  9. Al-Msie’deen R and Blasi A (2019). Supporting software documentation with source code summarization. International Journal of Advanced and Applied Sciences, 6(1): 59–67. https://doi.org/10.21833/ijaas.2019.01.008   [Google Scholar]
  10. Al-Msie’deen R, Huchard M, Seriai A, Urtado C, and Vauttier S (2014a). Automatic documentation of [mined] feature implementations from source code elements and use-case diagrams with the REVPLINE approach. International Journal of Software Engineering and Knowledge Engineering, 24(10): 1413–1438. https://doi.org/10.1142/S0218194014400142   [Google Scholar]
  11. Al-Msie’deen R, Huchard M, Seriai A, Urtado C, and Vauttier S (2014b). Reverse engineering feature models from software configurations using formal concept analysis. In the 11th International Conference on Concept Lattices and Their Applications, Košice, Slovakia: 95-106.   [Google Scholar]
  12. Al-Msie’deen R, Huchard M, Seriai AD, Urtado C, Vauttier S, and Al-Khlifat A (2014c). Concept lattices: A representation space to structure software variability. In the 5th International Conference on Information and Communication Systems, IEEE, Irbid, Jordan: 1-6. https://doi.org/10.1109/IACS.2014.6841949   [Google Scholar]
  13. Al-Msie’deen R, Ra’Fat A, Seriai A, Huchard M, Urtado C, Vauttier S, and Salman HE (2013b). Feature location in a collection of software product variants using formal concept analysis. In the International Conference on Software Reuse, Springer, Pisa, Italy: 302-307. https://doi.org/10.1007/978-3-642-38977-1_22   [Google Scholar]
  14. Al-Msie’deen R, Seriai AD, Huchard M, Urtado C, and Vauttier S (2013a). Mining features from the object-oriented source code of software variants by combining lexical and structural similarity. In the IEEE 14th International Conference on Information Reuse and Integration, IEEE, San Francisco, USA: 586-593. https://doi.org/10.1109/IRI.2013.6642522   [Google Scholar]
  15. Al-Msie’deen R, Seriai AD, Huchard M, Urtado C, and Vauttier S (2014d). Documenting the mined feature implementations from the object-oriented source code of a collection of software product variants. In: Werner C, Gao K, Reformat M, and Xu H (Eds.), SEKE: Software Engineering and Knowledge Engineering: 138-143. Knowledge Systems Institute, Vancouver, Canada.   [Google Scholar]
  16. Al-Msie’deen R, Seriai AD, Huchard M, Urtado C, Vauttier S, and Eyal-Salman H (2013c). Mining features from the object-oriented source code of a collection of software variants using formal concept analysis and latent semantic indexing. In the SEKE: Software Engineering and Knowledge Engineering, Knowledge Systems Institute Graduate School, Portland, USA. https://doi.org/10.1109/IRI.2013.6642522   [Google Scholar]
  17. AL-Msie’deen RF and H Blasi A (2021). Software evolution understanding: Automatic extraction of software identifiers map for object-oriented software systems. Journal of Communications Software and Systems, 17(1): 20-28. https://doi.org/10.24138/jcomss.v17i1.1093   [Google Scholar]
  18. Al-Msie'deen R (2008). A requirement model of local news WEB/WAP application for rural communities. Ph.D. Dissertation, Universiti Utara Malaysia, Changlun, Malaysia.   [Google Scholar]
  19. Alsuwaiket M, Blasi A, and Al-Msie'dee R (2019). Formulating module assessment for improved academic performance predictability in higher education. Engineering, Technology and Applied Science Research, 9(3): 4287–4291. https://doi.org/10.48084/etasr.2794   [Google Scholar]
  20. Ayobami AS and Osman SWR (2013). Functional requirements of mobile applications for fishermen. In the UACEE 2nd International Conference on Advances in Automation and Robotics–AAR'13. https://doi.org/10.2139/ssrn.2249720   [Google Scholar]
  21. Barker TT (2002). Writing software documentation: A task-oriented Approach. 2nd Edition, Longman Pub Group, New York, USA.   [Google Scholar]
  22. Boehm B and Turner R (2004). Balancing agility and discipline: Evaluating and integrating agile and plan-driven methods. In the 26th International Conference on Software Engineering, IEEE, Edinburgh, UK: 718-719. https://doi.org/10.1109/ICSE.2004.1317503   [Google Scholar]
  23. Booch G (2005). On creating a handbook of software architecture. In the Companion to the 20th Annual ACM SIGPLAN Conference on Object-oriented Programming, Systems, Languages, and Applications, Association for Computing Machinery, San Diego, USA. https://doi.org/10.1145/1094855.1094862   [Google Scholar]
  24. Bosch J (2000). Design and use of software architectures: Adopting and evolving a product-line approach. Pearson Education, London, UK.   [Google Scholar]
  25. Caballero L, Moreno AM, and Seffah A (2016). How agile developers integrate user-centered design into their processes: A literature review. International Journal of Software Engineering and Knowledge Engineering, 26(08): 1175-1201. https://doi.org/10.1142/S0218194016500418   [Google Scholar]
  26. Choi J, Lee Y, and Kim K (2014). Html5 based interactive e-book reader. International Journal of Software Engineering and Its Applications, 8(2): 67-74.   [Google Scholar]
  27. Choi JI, Heo H, Lim KY, and Jo IH (2011). The development of an interactive digital textbook in middle school English. In the International Conference on Future Generation Information Technology, Springer, Jeju Island, Korea: 397-405. https://doi.org/10.1007/978-3-642-27142-7_47   [Google Scholar]
  28. Constantine LL and Lockwood L (2002). Process agility and software usability: Toward lightweight usage-centered design. Information Age, 8(8): 1-10.   [Google Scholar]
  29. Davis FD (1985). A technology acceptance model for empirically testing new end-user information systems: Theory and results. Ph.D. Dissertation, Massachusetts Institute of Technology, Cambridge, USA.   [Google Scholar]
  30. Eyal-Salman H, Seriai AD, Dony C, and Al-Msie'deen RF (2012). Recovering traceability links between feature models and source code of product variants. In the Variability for You Workshop: Variability Modeling Made Useful for Everyone, Association for Computing Machinery, Innsbruck, Austria: 21-25. https://doi.org/10.1145/2425415.2425420   [Google Scholar]
  31. Hofmeister C, Nord R, and Soni D (2000). Applied software architecture. Addison-Wesley Professional, Boston, USA.   [Google Scholar]
  32. Islam M and Nofal M (2008). IMM-book: E-training material for the Edu wave system. Ph.D. Dissertation, Universiti Utara Malaysia, Changlun, Malaysia.   [Google Scholar]
  33. Jurca G, Hellmann TD, and Maurer F (2014). Integrating agile and user-centered design: A systematic mapping and review of evaluation and validation studies of agile-UX. In the Agile Conference, IEEE, Kissimmee, USA: 24-32. https://doi.org/10.1109/AGILE.2014.17   [Google Scholar]
  34. Kotonya G and Sommerville I (1998). Requirements engineering: Processes and techniques. John Wiley and Sons, Hoboken, USA.   [Google Scholar]
  35. Kruchten PB (1995). The 4+1 view model of architecture. IEEE Software, 12(6): 42-50. https://doi.org/10.1109/52.469759   [Google Scholar]
  36. Patton J (2002). Designing requirements: Incorporating usage-centered design into an agile SW development process. In the Conference on Extreme Programming and Agile Methods, Springer, Chicago, USA: 1-12. https://doi.org/10.1007/3-540-45672-4_1   [Google Scholar]
  37. Patton J (2004). Interaction design meets agility: Practicing usage centered design on agile development projects. In the Conference on Extreme Programming and Agile Methods, Springer, Calgary, Canada: 226-226. https://doi.org/10.1007/978-3-540-27777-4_48   [Google Scholar]
  38. Paz A and Boussaidi GE (2018). Building a software requirements specification and design for an avionics system: An experience report. In the 33rd Annual ACM Symposium on Applied Computing, Association for Computing Machinery, Pau, France: 1262-1271. https://doi.org/10.1145/3167132.3167268   [Google Scholar]
  39. Shneiderman B, Plaisant C, Cohen MS, Jacobs S, Elmqvist N, and Diakopoulos N (2016). Designing the user interface: Strategies for effective human-computer interaction. Pearson, London, UK.   [Google Scholar]
  40. Sommerville I (2016). Software engineering. 10th Edition, Pearson, London, UK.   [Google Scholar]
  41. Valacich JS and George JF (2019). Modern systems analysis and design. Pearson, London, UK.   [Google Scholar]