Figure 3 - available via license: CC BY
Content may be subject to copyright.
Source publication
Background: The comprehensive representation of functional requirements is a crucial activity in the analysis phase of the software development life cycle. Representation of a complete set of functional requirements helps in tracing business goals effectively throughout the development life cycle. Use case modelling is one of the most widely-used m...
Similar publications
![Figure 1. RE process [1]](publication/353253800/figure/fig1/AS:1045648631681024@1626313469610/RE-process-1_Q320.jpg)
Requirement Engineering (RE) aims to provide assurance that a software product can meet user needs. The RE phase is a stage that is carried out early in the software development phase of the System Development Life Cycles (SDLC). The main problem in software development is the accuracy of the requirements specifications generated in the RE phase. P...
Citations
... b) UML diagram design E-Voting website design using Unified Modeling Language (UML). UML used in E-Voting website design is usecase diagram, activity diagram and class diagram. 1) Use Case Diagram Usecase diagrams serve to explain the sequence of activities carried out by actors and systems to achieve a certain goal (Beimel & Kedmi-Shahar, 2019), (Iqbal et al., 2020). Figure 4 is a usecasediagram of an admin actor. ...
Voting is the most important part of choosing leaders in an organization or institution, especially for those of us who use a democratic system. The election of organizational leaders in Darunnajah is still carried out conventionally, elections still use paper to select organizational leaders which is carried out by recording and counting the name or picture of one of the candidates. Creating the Darunnajah Vote System in the form of a web application for the election of organizational leaders in the Darunnajah environment can speed up the voting process. The web application is built using PHP and MySQL with features of user management, class management, candidate management, and E-Voting. This study aims to build an e-voting system that is expected to provide voting results quickly, and accurately and can be monitored in real-time during the implementation of the leader election. This system development method uses a web application-based SDLC Waterfall model. Testing using the black box method, every feature contained in the Darunnajah Vote System application, namely the Admin Login feature, User Login, User Voting, and User Data Processing features runs normally and functions properly.
... Counseling needs were defined with the user during the interview. Next, analyze the system that will be expected through features and interfaces and develop an interaction system [18]. Stages of the process of developing procedures and selecting appropriate modeling techniques. ...
The development of information systems in currently preserve to adjustment and it was customized according to the problem domain. In this paper, we will describe the modeling language that is applied when developing an information system. The development of information systems has become a trend for the last decade. Various methods have been proposed with different characteristics. The counseling information system in this case was developed with an object-oriented approach. The strong motivation in this research is to answer the challenges and demands of system development. Modeling in system development explains various modeling languages starting with identifying problems with use case modeling languages (Use case Diagrams), simplifying problems with structured modeling (Class Diagrams), to building communication patterns or interactions between objects with one another (Sequence Diagram). Thus, the system built is able to describe the complexity of information systems, especially counseling information.
... That is why representing the player-task design for serious games is important to better motivate users and provide appropriate enforcement (Lim & Reeves, 2010). It has been reported that in use case diagrams it is not possible to represent functions that are not initiated by a user like notifications or events given by a system (Iqbal et al., 2020). Similarly, system related behavior or events cannot be represented in UML-AD diagrams. ...
System design is recognized as one of the most critical components of a software system that bridges system requirements and coding. System design also has a significant impact on testing and maintenance activities, and on further improvements during the lifespan of the software system. Software design should reflect all necessary components of the requirements in a clear and understandable manner by all stakeholders of the software system. To distinguish system elements, separation of concerns in software design is suggested. In this respect, identification of the user tasks, i.e., the tasks that need to be performed by the user, is not currently reflected explicitly in system design documents. Our main assumption in this study is that software quality can be improved significantly by clearly identifying the user tasks from those that need to be performed by the computer system itself. Additionally, what we propose has the potential to better reflect the user requirements and main objectives of the system on the software design and thereby to improve software quality. The main aim of this study is to introduce a novel notation for software developers in the frame of UML Activity Diagram (UML-AD) that enables designers to identify the user tasks and define them separately from the system tasks. For this purpose, an extension of UML-AD, named UML-ADE (UML-Activity Diagram Extended) was proposed. Afterwards, it was implemented in a serious game case for which the specification of user tasks is extremely important. Finally, its effectiveness was analyzed and compared to UML-AD experimentally with 72 participants. The defect detection performance of the participants on both diagrams with two real-life serious game scenarios was evaluated. Results show a higher level of understandability for those using UML-ADE, which in turn may indicate a better design and higher software quality. The results encourage researchers to develop specific design representations dedicated to task design to improve system quality and to conduct further evaluations of the impact of these design on each of the above mentioned potential benefits for the software systems.
Requirement specifications play an essential role in software development processes. They can take different forms, including a use-case model. The use-case model defines the use-cases and the relationships among them and contains definitions of the use-case specifications. It is used to estimate software development project efforts and for planning iterations. The use-case model is subject to change as requirements evolve or the model is refactored. Therefore, it is essential that the use-case model is not redundant and its parts are reusable. Existing approaches for the use-case model specification support reusability in a limited way. This paper fills the gap. It introduces a new Use-Case Flow Language to specify the entire use-case model conveniently yet semi-formally. The language is defined at the abstract syntax level by a metamodel with an informal description of the semantics of the metamodel elements. A discussion and justification of metamodel elements is given. A concrete textual syntax of the language is also provided and informally described. An example of a use-case model specified in the proposed notation is presented in the paper.
Microlending involves giving small loans to people in need. Usually, these loans are issued to entrepreneurs or those who need extra cash to either expand or for personal use. Digital lending is becoming a leading source of credit especially to low-income citizens with minimal or no financial footprints in various parts of the world. It has quickly become the default way for lenders to service loan requests from borrowers due to the convenience it brings about as well as the increased number of requests that can be processed compared to the traditional way that required quite an amount of paper work. As the number of lending companies grows, there is the need to standardize the credit scoring process and maintain an updated credit activity log for every user. This ensures that lenders are always aware of any other unsettled debts a borrower might have and provides them with the most recent information to assess the risk they face by lending to a borrower. The proposed solution consists of a credit scoring neural network-based algorithm composed of a single input layer, a single hidden layer and an output layer of one neuron, and a representational state transfer (REST) based web service allows lenders to submit details of loans they have approved and issued to a borrower. The information is used to generate and keep track of the user’s credit score and amount of risk lenders face should they consider lending to the user. Agile development methodology was used to develop robust credit scoring prototype and Android mobile application. The final prototype was tested to ensure that the requirements were met and the functionality working as required.KeywordsMicrolendingCredit scoringRepresentational state transferNeural networkMobile application
