Model and Process for Timely Progress Reporting in Use Case Driven Software Development

2004 ◽  
pp. 195-206
Author(s):  
Sungwook Moon ◽  
Joa Sang Lim
Keyword(s):  
Software Development ◽  
Use Case ◽  
Progress Reporting

scholarly journals SISTEM INFORMASI INVENTORY BARANG MENGGUNAKAN METODE WATERFALL

2021 ◽  
Vol 7 (1) ◽  
pp. 93-99
Author(s):  
Sopian Aji ◽  
Dany Pratmanto
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Sequence Diagram ◽  
Use Case ◽  
Activity Diagram ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Microsoft Office ◽  
Use Case Diagram

Pencatatan inventory barang atau produk yakni pencatatan pengeluaran dan pemasukan, pencatatan pengeluaran merupakan transaksi atau pesanan barang sesuai dengan pesan supplier atau customer kemudian dicatatan oleh tugas gudang, sedangkan pencatatan pemasukan merupakan penambahan stok barang atau produk atau produk mentah yang dicatatan oleh tugas gudang. Pada inventory barang yang diteliti oleh penulis ini dimana proses pencatatan pengeluaran dan pemasukan barang yang dilakukan masih manual dengan masih menggunakan microsoft office excel karena karena aplikasi tersebut tidak bisa menyimpan data dan informasi secara terpusat pada suatu database. Untuk mengatasi permasalahan tersebut penulis menggunakan proses yang sebelumnya manual menjadi terkomputerisasi sehingga pencatatan pengeluaran dan pemasukan barang informasi yang dihasilkan lebih tepat dan akurat dengan data ditampilkan secara terpusat sehingga lebih efektif dan efisien. Dalam pengembangan sistem yaitu Software Development Life Cycle (SDLC) dengan metode Waterfall yang berorientasi objek dan berbasis web, perancangan Sistem menggunakan tools desain United Modelling languange (UML) dengan perancangan use case diagram, activity diagram dan sequence diagram, sedangkan perancangan database menggunakan tools desain Logical Record Structure (LRS).

UCDiff: Difference Detection in Use Case Models of Healthcare System

2020 ◽  
Vol 10 (10) ◽  
pp. 2369-2377
Author(s):  
Waqar Mehmood ◽  
Hassan Jari ◽  
Ali Tahir ◽  
Waqar Aslam ◽  
Muhammad Kamran
Keyword(s):  
Software Development ◽  
Healthcare System ◽  
Model Comparison ◽  
Configuration Management ◽  
Use Case ◽  
Software Configuration Management ◽  
Difference Detection ◽  
Software Configuration ◽  
Use Case Models ◽  
Use Case Model

Development of large-scale healthcare software projects essentially need the efficient management of the created software artifacts during software development process. In such projects different versions of an artifact are created at different times. Traditional software configuration management systems, such as Git, Subversion (SVN), etc., are designed for later phases of software development, which mainly handle the source code document. These systems are unable to perform difference detection and version management tasks on models such as unified modeling language diagrams. UML use case model is used for capturing functional requirements at analyses phase. Different versions of the use case model are created during analyses phase. This paper addresses the detection of differences between two versions of a use case model. In order to perform difference detection, we need to perform three main tasks, i. e., extract the contents of the model, comparison of models and difference representation. Most of the existing approaches in literature of model comparison deal with UML class diagrams. To the best of our knowledge, so far no appropriate approach addresses difference computation of use case model. Existing approaches are not applicable on use case model due to different semantics of use case model. In this research, the concept of model-based software configuration management (SCM) for use case difference detection is proposed. The use case models are created in an open source tool, starUML. The proposed difference algorithm is applied on intermediate tree structure representation of models. As a case study, different versions of a patient appointment healthcare system is used to evaluate different evaluation parameters, such as accuracy, domain independence, high conceptual level and tool independence.

scholarly journals Perancangan Aplikasi Pembelajaran Bahasa Mandarin Dasar Menggunakan Metode Unified Software Development Process

2016 ◽  
Vol 9 (1) ◽  
Author(s):  
Andri Kulung ◽  
Steven Sentinuwo ◽  
Alicia Sinsuw
Keyword(s):  
Software Development ◽  
Development Process ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Use Case ◽  
Software Development Process ◽  
Unified Modeling

Bahasa Mandarin merupakan salah satu Bahasa yang terkenal di seluruh dunia. Ada sekitar 1.302 juta orang dengan berbagai kalangan umur telah menggunakan Bahasa mandarin, sehingga karena alasan tersebut banyak sekolah termasuk Sekolah Dasar (SD) Advent 1 Tikala Manado telah memasukkan Bahasa Mandarin sebagai salah satu mata pelajaran Bahasa asing. Namun siswa-siswa SD Advent 1 Tikala Manado merasa kesulitan dalam mempelajari Bahasa Mandarin dikarenakan tidak adanya media pembelajaran yang dapat membantu mereka dalam mempelajari Bahasa Mandarin di luar jam sekolah. Aplikasi pembelajaran Bahasa Mandarin Dasar merupakan solusi untuk membantu siswa SD Advent 1 Tikala Manado dalam mempelajari Bahasa Mandarin, baik dalam proses pembelajaran di sekolah maupun di luar sekolah. Unified Software Development Process (USDP) merupakan metode pengembangan perangkat lunak yang prosesnya dikendalikan oleh Use Case (use case driven) dan dikerjakan secara berulang (iterative) sehingga pada akhirnya menghasilkan perangkat lunak terintegrasi berukuran besar yang terbentuk secara bertahap (Incremental) dengan bantuan Unified Modeling Language (UML) sebagai alat bantu utama analisis dan perancangan sistem perangkat lunak. Aplikasi pembelajaran Bahasa Mandarin Dasar dibuat dengan fitur belajar dan bermain. Fitur belajar dilengkapi dengan materi pengajaran yang digolongkan ke dalam  beberapa kategori yaitu kategori kelas 1, kelas 2, dan kelas 3 serta sub fitur berupa suara dengan tujuan siswa bisa mengetahui cara pengucapan suatu kata. Dengan dibuatnya aplikasi ini diharapkan agar aplikasi ini bisa membantu siswa dalam mempelajari Bahasa Mandarin pada jam sekolah maupun diluar jam sekolah.

Use Cases in the UML

2011 ◽  
pp. 3909-3913
Author(s):  
Brian Dobing ◽  
Jeffrey Parsons
Keyword(s):  
Software Development ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Use Cases ◽  
Use Case ◽  
Unified Modeling ◽  
Systems Analysis And Design ◽  
Text Document ◽  
Management Group ◽  
Uml 2.0

The unified modeling language (UML) emerged in the mid-1990s through the combination of previously competing object-oriented systems analysis and design methods, including Booch (1994), Jacobson, Christerson, Jonsson, and Overgaard (1992), Rumbaugh, Blaha, Premerlani, Eddy, and Lorensen (1991) and others. Control over its formal evolution was placed in the hands of the object management group (www.omg.org), which recently oversaw a major revision to UML 2.0 (OMG, 2005). The UML has rapidly emerged as a standard language and notation for object-oriented modeling in systems development, while the accompanying unified software development process (Jacobson, Booch, & Rumbaugh, 1999) has been developed to provide methodological support for applying the UML in software development. Use cases play an important role in the unified process, which is frequently described as “use case driven” (e.g., Booch et al., 1999, p. 33). The term “use case” was introduced by Jacobson (1987) to refer to a text document that outlines “a complete course of events in the system, seen from a user’s perspective” (Jacobson et al., 1992, p. 157). The concept resembles others being introduced around the same time. Rumbaugh et al. (1991), Wirfs-Brock, Wilkerson, and Wiener (1990), and Rubin and Goldberg (1992) use the terms “scenario” or “script” in a similar way. While use cases were initially proposed for use in object-oriented analysis and are now part of the UML, they are not inherently object-oriented and can be used with other methodologies.

Effort Estimation Model for each Phase of Software Development Life Cycle

2012 ◽  
pp. 238-246
Author(s):  
Sarah Afzal Safavi ◽  
Maqbool Uddin Shaikh
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Cost Estimation ◽  
Use Case ◽  
Effort Estimation ◽  
Cost Overrun ◽  
Estimation Model ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
The Cost

The assessment of main risks in software development discloses that a major threat of delays are caused by poor effort / cost estimation of the project. Low / poor cost estimation is the second highest priority risk [Basit Shahzad]. This risk can affect four out of a total five phases of the software development life cycle i.e. Analysis, Design, Coding and Testing. Hence targeting this risk alone may reduce the overall risk impact of the project by fifty percent. Architectural designing of the system is a great activity which consumes most of the time in SDLC. Obviously, effort is put forth to produce the design of the system. It is evident that none of the existing estimation models try to calculate the effort put on designing of the system. Although use case estimation model uses the use case points to estimate the cost. But what is the cost of creating use cases? One reason of poor estimates produced by existing models can be negligence of design effort/cost. Therefore it shall be well estimated to prevent any cost overrun of the project. We propose a model to estimate the effort in each of these phases rather than just relying upon the cost estimation of the coding phase only. It will also ease the monitoring of project status and comparison against planned cost and actual cost incurred so far at any point of time.

DEVELOPMENTAL SIZE ESTIMATION FOR OBJECT-ORIENTED SOFTWARE BASED ON ANALYSIS MODEL

2013 ◽  
Vol 23 (03) ◽  
pp. 289-308 ◽  
Author(s):  
CHAMUNDESWARI ARUMUGAM ◽  
CHITRA BABU
Keyword(s):  
Software Development ◽  
Object Oriented ◽  
Use Case ◽  
Size Estimation ◽  
Model Function ◽  
Analysis Phase ◽  
Point Analysis ◽  
Function Point ◽  
Model Components ◽  
Use Case Model

Software size estimation at the early analysis phase of software development lifecycle is crucial for predicting the associated effort and cost. Analysis phase captures the functionality addressed in the software to be developed in object-oriented software development life-cycle. Unified modeling language captures the functionality of the software at the analysis phase based on use case model. This paper proposes a new method named as use case model function point to estimate the size of the object-oriented software at the analysis phase itself. While this approach is based on use case model, it also adapts the function point analysis technique to use case model. The various features such as actors, use cases, relationship, external reference, flows, and messages are extracted from use case model. Eleven rules have been derived as guidelines to identify the use case model components. The function point analysis components are appropriately mapped to use case model components and the complexity based on the weightage is specified to calculate use case model function point. This proposed size estimation approach has been evaluated with the object-oriented software developed in our software engineering laboratory to assess its ability to predict the developmental size. The results are empirically analysed based on statistical correlation for substantiating the proposed estimation method.

Sign in / Sign up

Export Citation Format

Share Document