Domain-Design Driven Approach to E-Meeting Application Development
Anggoro Ari Nurcahyo1, Ade Sukendar2
1Anggoro Ari Nurcahyo, Department of Informatic Engineering, Pasundan University, Indonesia.
2Ade Sukendar, Department of Informatic Engineering, Pasundan University, Indonesia.
Manuscript received on 05 June 2019 | Revised Manuscript received on 12 June 2019 | Manuscript Published on 19 June 2019 | PP: 221-226 | Volume-8 Issue-8S June 2019 | Retrieval Number: H10360688S19/19©BEIESP
Open Access | Editorial and Publishing Policies | Cite | Mendeley | Indexing and Abstracting
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open-access article under the CC-BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/)
Abstract: Meetings are used as a medium to discuss, negotiate and make a decision on a problem based, except that the function of the meeting is often not going well in the university’s faculty of informatics engineering. This happened because the results of the meeting were still scattered in several people and fields, so it was difficult to evaluate the results of the meeting, which eventually resulted in ambiguous meetings with no standardized decrees, rules, procedures that would overshadow every activity within the faculty. as well as the determination of the distribution of assignments specified in the meeting and the incentive burden. In designing this modern application, the approach that is often used is Domain-Driven Design (DDD). Applying and expanding the concepts and tasks of DDD is very challenging because it does not have a description of the software development process and classification in the software development process approach. For this reason, we provide a brief overview of the resource-oriented DDD-based software development process that takes into account the desired application requirements.
Keywords: Meeting, Domain-Driven Design, Software Development Process.
Scope of the Article: Automated Software Design and Synthesis