scholarly journals Requirements for development of cMOOC platforms from the professional's perspective

2021 ◽  
Author(s):  
Virginia de S. Venega ◽  
Rita Suzana Pitangueira Maciel
Keyword(s):  
Software Development ◽  
Knowledge Construction ◽  
Peer Collaboration ◽  
Software Requirements ◽  
Four Dimensions ◽  
Education Professionals ◽  
The Future

MOOC with a Connectivist approach (cMOOC) are heavily dependent on peer collaboration for knowledge construction. Requirements for elicitation for these environments are not a trivial task and should take different perspectives. This paper describes a study carried out with informatics and education professionals to identify the software requirements to compose cMOOC platforms. In this context, a questionnaire was applied and, after analysis, returned 116 requirements divided into 11 categories, coded in correlation with the four dimensions of connectivism. In the future, it is expected with this research to compose requirements catalogue to contribute to software development in cMOOC domain.

scholarly journals Selection and Prioritization of Software Requirements Applying Verbal Decision Analysis

Complexity ◽  
2019 ◽  
Vol 2019 ◽  
pp. 1-20
Author(s):  
Paulo A. M. Barbosa ◽  
Plácido R. Pinheiro ◽  
Francisca R. V. Silveira ◽  
Marum Simão Filho
Keyword(s):  
Software Development ◽  
Decision Analysis ◽  
Decision Maker ◽  
Development Process ◽  
Software Requirements ◽  
Software Development Process ◽  
Next Release Problem ◽  
Support Tools ◽  
Verbal Decision Analysis ◽  
The Cost

During the software development process, the decision maker (DM) must master many variables inherent in this process. Software releases represent the order in which a set of requirements is implemented and delivered to the customer. Structuring and enumerating a set of releases with prioritized requirements represents a challenging task because the requirements contain their characteristics, such as technical precedence, the cost required for implementation, the importance that one or more customers add to the requirement, among other factors. To facilitate this work of selection and prioritization of releases, the decision maker may adopt some support tools. One field of study already known to solve this type of problem is the Search-Based Software Engineering (SBSE) that uses metaheuristics as a means to find reasonable solutions taking into account a set of well-defined objectives and constraints. In this paper, we seek to increase the possibilities of solving the Next Release Problem using the methods available in Verbal Decision Analysis (VDA). We generate a problem and submit it so that the VDA and SBSE methods try to resolve it. To validate this research, we compared the results obtained through VDA and compared with the SBSE results. We present and discuss the results in the respective sections.

A Framework for the Generation of Class Diagram from Text Requirements using Natural language Processing

2021 ◽  
Vol 10 (1) ◽  
pp. 25-31
Keyword(s):  
Natural Language Processing ◽  
Software Development ◽  
Natural Language ◽  
Language Processing ◽  
English Language ◽  
Software Requirements ◽  
Class Diagram ◽  
Requirement Analysis ◽  
Part Of Speech ◽  
Software Engineers

The software development procedure begins with identifying the requirement analysis. The process levels of the requirements start from analysing the requirements to sketch the design of the program, which is very critical work for programmers and software engineers. Moreover, many errors will happen during the requirement analysis cycle transferring to other stages, which leads to the high cost of the process more than the initial specified process. The reason behind this is because of the specifications of software requirements created in the natural language. To minimize these errors, we can transfer the software requirements to the computerized form by the UML diagram. To overcome this, a device has been designed, which plans can provide semi-automatized aid for designers to provide UML class version from software program specifications using natural Language Processing techniques. The proposed technique outlines the class diagram in a well-known configuration and additionally facts out the relationship between instructions. In this research, we propose to enhance the procedure of producing the UML diagrams by utilizing the Natural Language, which will help the software development to analyze the software requirements with fewer errors and efficient way. The proposed approach will use the parser analyze and Part of Speech (POS) tagger to analyze the user requirements entered by the user in the English language. Then, extract the verbs and phrases, etc. in the user text. The obtained results showed that the proposed method got better results in comparison with other methods published in the literature. The proposed method gave a better analysis of the given requirements and better diagrams presentation, which can help the software engineers. Key words: Part of Speech,UM

What, Why, Who, When, and How of Software Requirements

2014 ◽  
pp. 1-18 ◽  
Author(s):  
Linda Westfall
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Software Requirements ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
The Right

If software requirements are not right, companies will not end up with the software they need. This chapter discusses the various levels and types of requirements that need to be defined, the benefits of having the right software requirements, the stakeholders of the software requirements and getting them involved in the process, requirements activities throughout the software development life cycle, and techniques for eliciting, analyzing, specifying, and validating software requirements.

Requirements Traceability

2010 ◽  
pp. 102-120
Author(s):  
Elias Canhadas Genvigir ◽  
Nandamudi Lankalapalli Vijaykumar
Keyword(s):  
Software Development ◽  
Change Management ◽  
Requirements Engineering ◽  
Software Requirements ◽  
Requirements Management ◽  
Requirements Traceability

This chapter presents a research about the Software Requirements Traceability. The main elements of traceability, definitions, problems and prospects are presented. The chapter is organized by topics and its beginning is a review about requirements engineering, its categories (Elicitation, Analysis and Negotiation, Documentation, Validation, and Management) and its role in software development. Afterwards, the requirements management and its elements (Identification, Change Management and Traceability) are described. Traceability is discussed; its aspects and problems are exploited as well as its classifications, techniques, links, metrics and models. Finally the Conclusion presents the main points that can be explored in future researches.

Dynamic Prioritization of Software Requirements for Incremental Software Development

2021 ◽  
pp. 111-131
Author(s):  
Mandira Roy ◽  
Novarun Deb ◽  
Agostino Cortesi ◽  
Rituparna Chaki ◽  
Nabendu Chaki
Keyword(s):  
Software Development ◽  
Software Requirements

Processes of Constitutional Transitions in the Face of Territorial Cleavages

2019 ◽  
pp. 330-351
Author(s):  
Cheryl Saunders
Keyword(s):  
Sri Lanka ◽  
Agenda Setting ◽  
Transition Process ◽  
Constitutional Amendments ◽  
Four Dimensions ◽  
The Future ◽  
The Face ◽  
The Postponement

This chapter discusses the implications of territorial cleavages for the process of constitutional transition by drawing on the experiences of various countries such as Bolivia, Bosnia-Herzegovina, Ethiopia, India, Iraq, Nepal, Philippines, Scotland, Spain, Sri Lanka, and Ukraine. It first considers four variables that are likely to affect the process for constitutional transition within a state in which there are significant cleavages along territorial lines: the nature of transition, the nature of territorial cleavage, the challenges confronting statehood, and the involvement of international actors. It then examines four dimensions of the processes of transition that may be influenced by territorial cleavages: phases of the transition process, agenda setting, deliberation and ratification, and implementation and other matters. Finally, it explains how constitutional transitions are shaped by the postponement of final decisions on key matters through deliberate ambiguity, incomplete prescription or reliance on the future operation of rules on constitutional amendments.

Sign in / Sign up

Export Citation Format

Share Document