scholarly journals Automating Software Develpoment using Artificial Intelligence.doc

2020 ◽  
Author(s):  
Sai Lohith Vasireddi ◽  
Mahesh Dhaka ◽  
Jinan Fiaidhi
Keyword(s):  
Software Development ◽  
Development Process ◽  
Research Paper ◽  
Team Formation ◽  
Software Development Process ◽  
Requirement Specification ◽  
Software Requirement ◽  
Software Requirement Specification

The research paper focuses on automating software development process by automating the team formation by extracting information from the software requirement specification (SRS) document of the project.

scholarly journals Automating Software Develpoment using Artificial Intelligence.doc

2020 ◽  
Author(s):  
Sai Lohith Vasireddi ◽  
Mahesh Dhaka ◽  
Jinan Fiaidhi
Keyword(s):  
Software Development ◽  
Development Process ◽  
Research Paper ◽  
Team Formation ◽  
Software Development Process ◽  
Requirement Specification ◽  
Software Requirement ◽  
Software Requirement Specification

The research paper focuses on automating software development process by automating the team formation by extracting information from the software requirement specification (SRS) document of the project.

scholarly journals Implementing Item-Based Collaborative Filtering System in Requirement Elicitation

2019 ◽  
Vol 8 (2S2) ◽  
pp. 230-233 ◽  
Keyword(s):  
Software Development ◽  
Collaborative Filtering ◽  
Development Process ◽  
Requirement Engineering ◽  
Vital Role ◽  
Software Development Process ◽  
Requirement Elicitation ◽  
Requirement Specification ◽  
Human Effort ◽  
Software Requirement Specification

In Requirement Engineering, Gathering Requirements plays a vital role in the Software Development Process. There are lot of processes available to gather requirements i.e. Brainstorming, Interview, Observation. This process takes lot of time and effort for the developer to gather and continue the development, and if the requirements which are analyzed are not up to the satisfaction of the user, it will cause issues in end product resulting in loss of human effort, time and cost. To overcome this issue faced by the developers we have developed a tool using item-based collaborative algorithm for users which will recommend users the required set of functional and nonfunctional requirements based upon the questionnaire given tothe user and produce a software requirement specification (SRS).

scholarly journals Tailoring effective requirement's specification for ingenuity in Software Development Life Cycle.

2021 ◽  
Vol 12 (3) ◽  
pp. 3338-3344
Author(s):  
Naveen N Kulkarni Et.al
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Natural Language ◽  
Development Process ◽  
Object Oriented ◽  
Software Development Process ◽  
Software Documentation ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Software Requirement Specification

Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include  incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain need to be developed. So software  documentation is completed in such a way that, all authorized users like clients, analysts, managers, and developers can understand it. These are the basis for success of any planned project. Most of the work is still dependent on intensive human (domain expert) work. consequences of the project success still depend on timeliness with tending errors. The fundamental quality intended for each activity is specified during the software development process. This paper concludes critically with best practices in writing SRS. This approach helps to mitigate SRS limitation up to some extent. An initial review highlights capable results for the proposed practices

scholarly journals Are UX Evaluation Methods Providing the Same Big Picture?

Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  
Keyword(s):  
Software Development ◽  
Decision Process ◽  
Development Process ◽  
Evaluation Methods ◽  
Sentence Completion ◽  
Software Development Process ◽  
Software Application ◽  
Software Products ◽  
Big Picture ◽  
The Impact

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.

Sign in / Sign up

Export Citation Format

Share Document