Đang tải... (xem toàn văn)
Điểm của bài asm còn tùy thuộc vào người chấm. Chỉ cần paraphase bài này là có thể pass. 1 trong nhưng tool paraphase mình recommend là quillbot.The submission is in the form of 1 document.● You must use the Times font with 12pt size, turn on page numbering; set line spacing to 1.3 andmargins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation andreferences must follow the Harvard referencing style. ASSIGNMENT FRONT SHEET Qualification BTEC Level HND Diploma in Computing Unit number and title Unit 2: Networking Infrastructure Submission date Date Received 1st submission Resubmission Date Date Received 2nd submission Student Name Student ID Class Assessor name Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism I understand that making a false declaration is a form of malpractice Student’s signature Grading grid P1 P2 P3 P4 M1 M2 D1 ❒ Summative Feedback: Grade: Lecturer Signature: ❒ Resubmission Feedback: Assessor Signature: Date: Table of Contents I Network Network definiton Ξ First of all, network also known as computer networking, which can be understand as a group of computers utilizing a principles of general communication protocols over digital connections for the intention of sharing resources located upon or accommodated by network nodes ... https:www.dnsstuff.comdatabreach 10 1 Dobran, B., 2 019 Information Security Risk Management: Build a Strong Program Online Available at: https:phoenixnap.combloginformation security riskmanagement garg, r., 20 21 Threats... List and give examples with dates 12 Propose a method to assess and treat IT security risks (M1) 18 TASK DESCRIBE AT LEAST ORGANIZATIONAL SECURITY PROCEDURES (P2) .20 Definition... Dan Swinhoe, 20 21 The 15 biggest data breaches of the 21st century, s.l.: s.n Ohri, A., 20 21 What Is DMZ Network Online Available at: https:www.jigsawacademy.comblogscyber security whatisdmz ASSIGNMENT FRONT SHEET Qualification BTEC Level HND Diploma in Business Unit number and title Unit 30: Application Development Submission date 27122022 Date Received 1st submission Resubmission Date Date Received 2nd submission Student Name Nguyen Huy Hoang Student ID GCH200739 Class GCH0908 Assessor name Dinh Duc Manh Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism I understand that making a false declaration is a form of malpractice Student’s signature Grading grid P4 P5 P6 M3 M4 M5 D2 D3 Summative Feedback: Grade: Assessor Signature: Resubmission Feedback: Date: Internal Verifier’s Comments: Signature Date: Table of Contents Task – Peer Review and Feedback Analysis (P4 – M3) I Introduction II Peer review and feedback analysis List of questions Review and Interpret feedbacks Evaluate any new insights, ideas or potential improvements 16 Task – Application Development (P5, M4) 17 Folder structure of the application 17 Source code samples of the application 19 Order Management Cart Checkout Owner feature: 19 Other Controller: 24 View: 26 Final screenshot 28 Screenshots of using GitHub to manage the source code 48 Task – Application Evaluation (P6 – M5) 53 Performance of the application 53 Customer 54 Store Owner 61 Admin 66 Strengths and weaknesses of the application 69 Gantt chart 71 Task – Peer Review and Feedback Analysis (P4 – M3) I Introduction The projects creator will present and describe the system in this second section while also gathering data from a survey We sell books on our FPTBook, an online library, for a profit We, a threeperson team, collaborate to create this website II Peer review and feedback analysis List of questions Question Scope Open Question Add about the experience of user when using FPTBook Closed Question Ask about the experience in Homepage in which the books are showed Closed Question Ask about the detail pages Closed Question Ask about the store owner page Closed Question Ask about admin page Open Question Add about point of view of user when using it Closed Question Add about login feature Review and Interpret feedbacks The survey states that this section is to find out 12 participated in the survey According to the results, 60% of respondents prefer our project in the range of to 5, while 40% fall into range This means that practically everyone has been pleased with our method The responses to this query show us that the system has only almost pleased everyone, most features are take opinion of 33.3% normal and 66.7% good We take pride in the fact that our systems user interface scored 100% on scales and That indicates that our page is attractive and appealing Sign in page: In terms of UI design, the login page features a nav bar that the factor page does not The layout of the factor page is superior to that of the UI design page since it has more icons, colors, images, and suitable buttons with links The Sign In page is superior than the UI Design page Profile page, Checkout page, Order page: The user has a profile page in UI design where they may examine their info and cart However, the user just has an order page where they may see their order on the real website In UI design, users have a Checkout page where they can verify their order, which has the same purpose as the order page but a nicer layout Because it has greater information and usefulness, UI design is superior than page design Store Owner Delete a book in book list: The delete function in UI design and the factor design seem to be the same Book Detail: The UI design of the book detail page is minimal and does not contain many functions, unlike the factor page It does not mention the route to the product page, book category, or book title The book detail page is superior than the UI design page Add new book: The UI design for adding a new book is minimal, with few functions and data fields compared to the real page The add new book page is superior than the UI design page Update book page: The update book page of UI design is simpler and has fewer functions and data fields than the factor page, making it superior to the UI design page Customer order page: Because of its clever and scientific arrangement, the customer order book page of UI design outperforms the order book design The customer order book of UI design outperforms factor design Make request category page: Make request genre page design does the same purpose as UI design but has a superior layout Genre list page: The genre list design is where users may browse available genre in the database and see whether admin accepts or rejects their genre request Admin Detail page for customer and storeowner: The UI design page has a detail page where they may check customer and storeowner data and change their account password if necessary, however the factor design page does not Request category: Request category page design does the same job as UI design page but has a superior layout Delete, update, new roles: The role control page design performs the same function as the UI design page but has a better layout Strengths and weaknesses of the application Strengths: ☺ The websites operations are generally logical, consistent, and comprehensive The components of the page are not redundant, and they all work in tandem Minimalized design but also provide an eyecatching design Web responsive also is good ☺ Their function and significance from customer interface to user experience ☺ Website Pages all provide an excellent user experience, including database processing The site pages are arranged in a logical order ☺ The content on the website is completely focused on the fundamental objective of the page, with no frills or distractions ☺ The user interface is nearly never malfunctions or crashes due to any flaws ☺ The security (authentication and authorization) has been designed pretty good by integrating with Identity Platform ☺ The navigation on this page is welldesigned There are no stuck pages, and all of the pages are in the exact order ☺ Controller operates pretty well Call controller actions via router are hardly getting errors Additionally, it is feasible to reroute the same content group Its possible to redirect to another page ☺ No webpage has been broken, no webpage has been unstructured, and no data from the model has been misplaced Ascertain that users obtain accurate data Weaknesses: The validation of the system is not really good Some web pages have been designed obsolete and sparing The loading speed of the website is really slow Some website functions (searching for productscategorybrand, adjusting the number in cart) that are not optimized may create a bad user experience Lack of functional option for users, the website is still quite sketchy in providing users with features, smart filters as well sorting functions by many different criteria The system has some minor typographical and syntactic errors The system is still operational, and functions such as the shopping cart and access to user information should not be prohibited if the account or password is wrong Improvement in Future With time, the FPTBook will need to be enhanced to include a module for email notifications In the future, the system will also be developed and implemented in Java so that it may be installed as an executable file Additionally, articles and research papers will be stored in a portion of the system The system will be enhanced to include an area for online book purchases and to show a photo of the individual who signs in Implementing a shopping cart into the library management system will make this feasible Making it possible to increase the number of times a book may be borrowed from the library system would also help the system Users will be able to borrow the same book more than once thanks to this The following are the upcoming projects that will be completed in the future: ➢ A customers may create a generic installation method that could be used to the installation of ASP.Net applications like the big popular library management system ➢ A customers may create a Distributed Health Management System that can integrate ASP.Net systems like the Library Management System, as well as an Information Management System that can combine ASP.Net systems like that ➢ The Library Management System, for example, may be integrated with a students Warehouse Management System using ASP.Net Future plans for this facility include the addition of many more features, including the ability for teachers to add online lectures and video tutorials, as well as the ability for customer to submit assignments online Another feature that could be added is group chat, which would allow customers to discuss a variety of engineeringrelated topics Gantt chart Week No Task name Title Project Preparation Assigned to 1.1 Meeting to choose Net core version HienHD 1.2 Set up project from scratch HoangNH 1.3 Analysis Business Process for coding HoangNH, HienHD 1.4 Gather and prepare UIUX Design TuND InitiationPlanning 2.1 Project Planning, assign tasks All team 2.2 Technical Specification All team 2.3 Design Database architecture All team Development 3.1 Buildcustomer authentication policy base with identity platform HoangNH 3.2 Build authorization with role management HienHD 3.3 Design book, category management TuND 3.4 Design order management HoangNH Week Week Mon Tue Wed Thur Fri Sat Mon Tue Wed Thur Fri Sat Mon Tue Wed Thur Fri Sat 3.5 Build category request functionality 3.6 Build account management for admin functionality HienHD 3.7 Build owner page with functionality HoangNH 3.8 Designbuild layout for website TuND 3.9 Build Cart, Checkout functionality HoangNH 3.10 Build Authorization in views HienHD HienHD 3.11 Complete Owner functionalities HoangNH 3.12 Complete Admin functionalities HienHD 3.13 Design style for pages TuND QA 4.1 Testing TuND 4.2 System Test All Team 4.3 Design review All Team Implementation 5.1 Deployment All Team Conclusion 6.1 Outcome Document Project Completed CONCLUSION TuND The library system was put into place, and it complied with all the standards Data validation and error checking were adequately handled by this system, however other aspects of software engineering testing were not fully completed owing to time constraints I was able to effectively finish the project and present a system that is operating and meets the system requirements even though there was not enough time to develop and construct the system From a personal standpoint, this project has really helped me understand how the theories and techniques I learned in class—like software engineering and programming—actually work Additionally, creating this system has really aided me in building my confidence in ASP.NET programming, JavaScript scripting, and project management
ASSIGNMENT FRONT SHEET Qualification BTEC Level HND Diploma in Business Unit number and title Unit 30: Application Development Submission date 24/12/2022 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Nguyen Huy Hoang Student ID GCH200739 Class GCH0908 Assessor name Dinh Duc Manh Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism I understand that making a false declaration is a form of malpractice Student’s signature Grading grid P1 P2 P3 M1 M2 D1 GCH200739 – Nguyen Huy Hoang GCH200739 – Nguyen Huy Hoang Summative Feedback: Resubmission Feedback: 3.1 Grade: Assessor Signature: Date: GCH200739 – Nguyen Huy Hoang Internal Verifier’s Comments: Signature & Date: GCH200739 – Nguyen Huy Hoang Software Requirements Specification for FPTBook Library Prepared by Group Members: • • • Nguyen Duc Tu – GCH200690 Nguyen Huy Hoang – GCH200739 Hoang Dinh Hien – GCH200791 GCH200739 – Nguyen Huy Hoang Table of Contents I Introduction Document purpose .9 Product scope Intended audience and document overview Definitions, acronyms, and abbreviations 10 II Overall descriptions (P1) 13 Product overview .13 Product functionality 13 Store owner 13 Customer .14 Admin 14 III Specific requirements(P1, P2) .14 Functional requirements 14 Use case model 18 Wire flow 19 Other pages 20 Customer .26 Store owner 28 Admin 34 IV Technical design(M1) 39 GCH200739 – Nguyen Huy Hoang Entity relationship diagram (ERD) 39 Class diagram 40 Admin diagram 40 Store owner diagram .41 Customer diagram 42 Activity diagram 43 Admin diagram 43 Gantt chart 45 V Risk assessment 49 Risk assessment 49 VI Evaluation report (P3, M2) 57 Design tools .57 1.1 Tool to design UML 57 1.2 Justify and Evaluation The Use of Our Preferred Selected UML design tool 63 Tools to design user interface wireframe 64 Tools to design the application 65 Justify and Evaluation the Use of Front end technology stack 70 Back-end technology stack 74 Back-end programming language/Framework 74 Operating system 77 Web Server 78 GCH200739 – Nguyen Huy Hoang Hosting 78 Database 80 Architectural Pattern Model 81 Tools for source control management 84 Software development models 85 Illustrate all Your Findings on How to Use These By Drawing The Overview 90 VII References 91 GCH200739 – Nguyen Huy Hoang I Introduction Document purpose This report gives an overview about the software requirement specification which specifies system architecture and business processes design of an online library that our group produced Version 1.0 of this document is now available The whole mechanism is explained in this SRS Readers will have a greater grasp of the system, the business challenge, and its solutions after reading this article We'll discuss technology design and risk assessment later Product scope The library selection offered by FPTBook is designed to be appealing to people of all ages We try to provide a wide range of literature, from children's books to novels on morality Since the beginning of the literature, there has been a globe representing the whole world Customers that regularly subscribe get access to all books Our objective is to get entry to a trustworthy intelligence source The works' legal copyright protection will take care of customers' worries Our present objective is to elevate the FPTBook collection's standing around the world We want to break even on the library within the first year of operation, or possibly even lose money Then, in order to grow our income, we aim to build a robust and active community It is very helpful for any educational institution where content modifications may be made easily in accordance with needs The project is simple to execute in a variety of circumstances, and because all of the modules are interchangeable, we are able to add new features as and when we are needed C# was chosen as the language to employ for the project's development because it has several advantages over other languages in terms of performance, tools, cross-platform compatibility, libraries, cost 1, free availability 2, and the development process Intended audience and document overview Our team will act as the client and developer in this project, and our teacher will also assume the client position Functional requirements, use cases, diagrams, Gannt charts, and risk assessment are all covered in this SRS There will be several more, one of which will be for individual examination Briefly, in real-world case study, this document is intended for developers, project managers, testers, etc GCH200739 – Nguyen Huy Hoang Definitions, acronyms, and abbreviations a) Entity Relationship Diagrams (ERDs): A kind of structural diagram used in database architecture are entity relationship diagrams (ERDs) Other names for them include ER Models, ER Diagrams, and ERDs The many symbols and connections on an ERD graphically represent the core elements included in the system scope as well as their connections (Visual Paradigm, 2022) Data structure diagrams (DSDs), which emphasize interactions between components inside entities rather than relationships between things themselves, are linked to ER diagrams ER diagrams are often combined with data flow diagrams (DFDs), which depict the information flow for systems or processes b) SRS: A software requirements specification (SRS) is a document that outlines the criteria for how the system must operate (tutorialspoint, 2022) Simply said, a need is a condition that must exist for a user to solve a problem or accomplish a goal It is the first phase of system development 10 GCH200739 – Nguyen Huy Hoang To increase availability, quickly deploy data and host services to several locations across the world To handle peak workloads, Microsoft Azure encourages automated horizontal and vertical scaling based on app performance and programmable criteria Their recently released computing option D-series is also available to meet the performance and scalability needs of your project Through, Azure Monitor, I can see detailed statistics on resource consumption as well as the throughput, CPU usage, memory, error trends, and response times of your application Benefit from hybrid consistency by building and managing apps on both on-premises and cloud infrastructure Azure supports enterprise-level SLAs and complies with security standards including ISO, PCI, and SOC2 Connect to a huge variety of cloud-based SaaS programs, including Dropbox, Salesforce, Office 365, Concur, and more → Microsoft Azure is selected because it’s quick and flexible: It takes far less time than I may imagine to develop, test, deploy, and manage software and applications on Azure Compared to IBM or Google Clouds, it is far quicker Businesses in Azure that are experimenting with new concepts and commercial prospects are prospering Businesses are implementing rapid innovation while keeping a sufficient amount of control and flexibility Additionally, compared to traditional internet connections, Azure ExpressRoute connections are more dependable and swifter Microsoft controls every aspect of infrastructure and security improvements for organizations, providing them the most cost-effective options possible As a well-known Microsoft Azure consultant Database +) SQL Server 2019: 80 GCH200739 – Nguyen Huy Hoang With SQL Server 2019, modern data professionals will be able to store corporate data in a data lake and perform SQL and Spark queries Less Extract, Transform, and Load (ETL) programs are needed since data movement is no longer required Because it is user-friendly and efficient, we decided to utilize Microsoft SQL Server 2019 to manage the database Architectural Pattern Model 5.1 List of Models Paradigms and compare between them: ❖ MVC: Model, View, and Controller are the three primary logical components that are divided into an application by the MVC Framework, an architectural pattern (Martin, 2022) MVC is hence an abbreviation Model View Controller is the acronym for this phrase 81 GCH200739 – Nguyen Huy Hoang In this design, a component is created to manage certain application development elements The business logic layer and presentation layer are separated by MVC Its primary use is in desktop graphical user interfaces (GUIs) ❖ MVVM: The usage of markup language or GUI code to separate the creation of the graphical user interface is made possible by the MVVM architecture Model-View-View Model is how MVVM is formally referred to The MVVM view model is a value converter, which means that it is up to the view model to expose the data objects from the Model in a form that makes them simple to manage and show ❖ Compare the differences between these twos: Attribute Architecture Working Principle Applications Uses MVC The user interface, which divides an application into three internally related components such a controller, view, and model, is developed using the infrastructure sequence The MVC architecture is built on the idea that the model represents the data, the view defines the user interface, and the controller controls the request It is used by Java, Spring, Asp, and NET Asynchronous requests are supported by MVC, and changes to the system don't affect the whole program MVVM The infrastructure sequence makes it easier to separate the graphical user interface that comes built-in from the business logic and back-end logic In MVVM, the view specifies the user interface, whereas the model defines the objects and entities View Model explains how the view and model are combined It is used by Microsoft APF, Angular JS, and Silverlight Offering separate testing units is MVVM This whole system's parts operate separately Internal parts may be replaced without impairing the performance of the system as a whole 82 GCH200739 – Nguyen Huy Hoang Input Data The controller controls the MVC's input Mapping The connection between controller and view is established using multiple to a single relation The MVC view was created to specify the user interface; the controller has no bearing on it Function of View Function of Controller The controller receives functions from the view, but the model is not given any logic by the controller Different and one view model create an excessive number of links One too many connections are provided by different and one view model Every reference to the view information in MVVM is stored in the view Some views on View Model are shared by the WCF and Silverlight View functionality is completely unaware of the model 5.2 Justify and Evaluation The Use of Selection: In ASP.Net, the two patterns appear in many ways Data inside views is two-way bound for ASP.Net using MVVM Typically, this is implemented on the client side (e.g using Knockout.js) On the other hand, MVC is a technique for dividing server-side responsibilities The issue is that a viewmodel must be completely opaque to the view that is presenting it in order to be independently testable and, more crucially, reusable when necessary In actual use, the majority of the View Model’s functionality that necessitates unit testing is removed by Controllers The VM then turns into a simple container that needs little to no testing This is advantageous because the VM should be kept basic as it just serves as a conduit between the designer and the programmer Even with MVVM, controllers often house all processing code and choose which view models to use for which views and which data to show According to what we've seen so far, the key advantage of the View Model approach is that it allows XAML changes to be done independently by removing code from the code-behind We continue to develop controllers as and when necessary to regulate (pardon the pun) the overarching logic of our apps So, the best model to implement the FPT Book Web app is MVCVM The fundamental MVCVM principles we adhere to are: • Views provide data in a certain shape They are unsure about the source of the data 83 GCH200739 – Nguyen Huy Hoang • • • • ViewModels store data and instructions in a certain form; they are unaware of the source of the data or code or the display strategy Models include the relevant data (various context, store or other methods) Controllers publish and listen for events The logic that determines where and how data is viewed is provided by controllers In order for the ViewModel to be really reusable, controllers provide it the command code We also pointed out that the Sculpture code-gen framework uses a lot of controllers to isolate the use-case logic and that it supports MVVM Another advantage of employing an MVCVM model is that just the controller objects, which mostly consist of code and minimal state data, need to remain in memory during the duration of the program (i.e., tiny memory overhead) This is appropriate for certain forms of mobile development (for example, Windows Mobile utilizing Silverlight/Prism/MEF), since it results in significantly less memory-intensive applications than alternatives where view-models must be preserved Of course, the sort of application will determine whether or not you need to sometimes keep cached virtual machines around for responsiveness Tools for source control management +) Git A local clone of the project is a full version control repository since Git is a distributed version control system Work may be done offline or remotely with ease thanks to these fully working local repositories Developers sync their local repository with the server's repository after committing their local work In contrast to centralized version control, which requires clients to synchronize their code with a server before producing new versions, this model does not need this Git is a fantastic option for any team because to its adaptability and ubiquity 84 GCH200739 – Nguyen Huy Hoang Many programmers and recent college grads are already proficient with Git Git's user base has produced training materials, and because to its popularity, getting assistance when you need it is simple Git support and Git command line tools are present in almost every development environment and on every major operating system Software development models 5.1 List of Software Development methodologies and Comparing the Differences Between Them ❖ Waterfall We will thus begin with the waterfall technique out of all the software development methods The cascade is quite chronological and linear Each procedure happens in stages while using a waterfall software development technique Furthermore, the first step must be finished before moving on to the next When the scope is really clear-cut, waterfall development is necessary (Senson, 2021) Additionally, the project remains unchanged It is thus expensive to go back after the project's early phases have been completed by the developers Different Waterfall Phases, the following are the basic stages for creating a project using the waterfall methodology: • • • • • • • • Concept: Having a distinct idea of the required product is crucial If you are working for a customer, be sure you have all the facts and fully understand their goals Providing thorough documentation is one of the crucial first tasks in the waterfall methodology Conduct a thorough examination of the project Budget, risks, dependencies, a completion date, and success measures should all be included Design: Finish writing up your reference material for the programming language you want to use The project's design and all of its design components must be chosen by the developer Implementation: The last stage is to construct your program and make your concept a reality Testing: Carefully test your product and look for software flaws Deploy: Deploy the work you are doing for the wider public, a business, or a customer After your project is finished, you will need to routinely maintain it, check it for bugs, and correct them as necessary 85 GCH200739 – Nguyen Huy Hoang • Requirements, Design, Implementation, Verification, and Maintenance are the stages of the waterfall model Major Waterfall Model Advantages • • • Changes are less of a concern while employing a waterfall paradigm for software development Both you and the customer would know exactly what to anticipate It is also simple to handle the time restrictions and job needs The project's cost may also be determined with accuracy Cons • • • • • • • If adjustments are necessary, it would be expensive and time-consuming to implement the approach since it is very non-dynamic It is difficult for stakeholders or customers to evaluate the project and provide input since no real products exist until late in the project The client-side might become less trusting of this strategy The outcome of the project would benefit if the project's original requirements were incorrect in any way Waterfall methodology used most effectively It works best for simple, brief jobs If the specifications are exact and transparent If the project involves crucial management systems, such as banking software, ❖ Scrum One of the most widely utilized Agile approaches among project managers is scrum project management Griffin explains that Scrum is a particular technique for managing a project, while Agile is a concept or mindset "It offers a procedure for how to identify the task, who will perform the work, how it will be done, and by when it will be finished," the author says 86 GCH200739 – Nguyen Huy Hoang In Scrum project management, the product owner, Scrum master, and other cross-functional team members make up the project team under the direction of the project manager The product owner is in charge of increasing the product's value, while the scrum master is in charge of making sure that the project team adheres to the Scrum approach When working on a project, the Scrum technique is characterized by brief "sprints" or stages The project team determines a small portion of the scope to be finished during the forthcoming sprint, which is typically a two-to-fourweek period of time, during sprint planning This work needs to be prepared to be given to the customer at the conclusion of the sprint The sprint concludes with a retrospective and sprint review, or rather, lessons learned Until the complete scope has been provided, this cycle is repeated throughout the project's lifespan This is similar to conventional project management in many respects But one of the significant distinctions is that instead of delivering everything at the end, "shippable" components of the project are created along the way By doing this, the customer can see the worth of the project early on rather of having to wait until it is finished to see the outcomes Advantages: • The development team controls the decision-making process • reduces the number of paperwork needed • reduces the size of enormous projects so that each component may be structured as a scrum of a scrum • To achieve a high-quality end result, testing is done often during the process Disadvantages: • Owing to frequent reviews and daily scrum sessions, requires a significant amount of resources • Not appropriate for large projects requiring numerous teams to accomplish You must divide the project into smaller scrums if many teams are necessary in order to facilitate simpler decision-making within the team • need a team of professionals; those who are new to the subject will have difficulty keeping up with the quick pace • intense project cycle brought on by a lot of modifications, a hazy product, and a lot of product delivery • high levels of team communication are necessary ❖ Comparing between Waterfall and Scrum: 87 GCH200739 – Nguyen Huy Hoang Scrum Waterfall At each stage, customers and stakeholders are involved By regularly analyzing the development process's sprints, scrum development saves time and money Teams are formed to split the work into separate responsibilities Product owners and stakeholders are consulted throughout the scrum process Throughout the development process, the client is regularly consulted and kept in the loop Scrum is a development methodology that excels at handling challenging and intricate projects There are no definite phases This keeps the client at a distance By the time the outcome is close It could take longer since just the results are reviewed; if the results are deemed improper, the procedure returns to level The work is broken up into stages The group collaborates well The necessary paperwork is completed at the beginning Only at the prerequisite step the proper documents get created Scrum is open to adjustments both early and late in the development process The option to edit anything afterwards is not available Each step and procedure is finished separately It breaks up the task into phases, which are completed one after the other It is not constrained by a short time frame As the consumer is aware of every action or development pertaining to his product, he is also not in a hurry to purchase the program Every stage of the project development is communicated to the client Smaller projects benefit from the waterfall methodology The waterfall model divides the project into distinct and well-defined phases Only at the prerequisite phase does it accept adjustments The team divides up the development process individually; no step is finished before moving on to the next It breaks up its work into sprints, which are subsequently distributed among the team members Early on, the client is shown a working version of the program Changes are a good thing for this reason Only the client is provided with functional software at delivery time There is a strict deadline associated with the waterfall development method Only on the day of delivery will the client be contacted 88 GCH200739 – Nguyen Huy Hoang 5.2 Justify and Evaluation the Use of Selected Research Methodology: The Waterfall is selected for our project, which is the undisputed methodology for theory and practice, according to Cerrone (2007) Following the Waterfall process guarantees a successful implementation According to the Waterfall technique, actions within the following five process categories take place throughout a project: • • • • Beginning procedures that are aimed towards obtaining approval for a project or one of its stages Planning procedures that specify goals and choose the actions to be taken to achieve project objectives Carrying out procedures needed to synchronize tasks, personnel, and other resources in order to implement the plan Monitoring and controlling activities that set the stage for measuring and tracking project outcomes in order to avoid deviations from the plan or to change course when a deviation does occur Closing procedures that formally acknowledge project acceptance and put a stop to project operations There are a total of 44 distinct detailed actions that are included in the five process categories Furthermore, depending on the goal, specific tasks may be used in many ways Complexity is where Scrum and the Waterfall technique diverge most In order to manage the project effectively, Scrum is better suited for large-scale projects and necessitates expertise and the capacity to apply particular activities to a variety of processes (Cervone, 2007) The Waterfall Method, on the other hand, offers flexibility for managing both large- and small-scale projects while being straightforward and practical According to Oura and Kijima (2001), the waterfall approach is used top down in that the development process can only go forward with management approval for each step If the organization is bottom-up and changes are made by employees at lower levels, this can be a problem The Waterfall technique is perfect for project libraries webapp development because it offers a straightforward methodology Phases are separated in the development process using the waterfall method The strategy, design, implementation, and operations phases of the suggested method adaption for library projects will be described Each stage contains a set of tasks that result in deliverables that management or regulatory bodies may use as proof documentation To create relevance and provide a foundation for progress reporting to higher management, the phases are assigned a percentage The scope of the library project is considered and examined during the plan stage It is necessary to determine the project's viability, user needs, the present process's map, the team's charter, and whether management would approve the purchase The Feasibility Phase and Requirements Specification stated in the Waterfall Methodology are equivalent to this step The Waterfall approach is fairly straightforward, as we can see Every endeavor and field, including education, may use it The system is so adaptable that it might be used to handle research proposals, inquiries, and even operational plans, but as in library sciences, those who apply it face difficulties because to the paucity of information in the field of 89 GCH200739 – Nguyen Huy Hoang education The absence of theory has made education and training more challenging and has impeded the successful professionalization of project management, according to Koskela and Howell (2002) Project management cannot and will not be given a respectable position in higher education institutions because it lacks theory Additionally, the spread of project management techniques into practice has been held back by the absence of a theory that would explain project management Particularly in the fields of engineering, software development, building, architecture, and telecommunications, there is a wealth of material available on project management techniques These fields have changed project management throughout time, although practitioners rather than educators are more likely to adopt project management techniques in the business world (HoonKwal & Anbari, 2009; Koskela & Howell, 2002) Because practitioners utilize project management techniques on a regular basis, but higher education institutions not employ them as often as we would want, this creates a contradiction between practice and research To determine why academics are not using project management techniques, further investigation and analysis must be conducted Illustrate all Your Findings on How to Use These By Drawing The Overview 90 GCH200739 – Nguyen Huy Hoang VII References Heller, M., 2022 What is Visual Studio Code? Microsoft’s extensible code editor [Online] Available at: https://www.infoworld.com/article/3666488/what-is-visual-studio-code-microsofts extensible-code-editor.html [Accessed 10 October 2022] The Economic Times, 2022 What is 'UML' [Online] Available at: https://economictimes.indiatimes.com/definition/uml [Accessed 10 October 2022] tutorialspoint, 2022 Software Requirement Specification [Online] Available at: https://www.tutorialspoint.com/software_testing_dictionary/software_requirement_specification.htm# [Accessed 10 October 2022] TutorialsTeacher, 2022 .NET Core Overview [Online] 91 GCH200739 – Nguyen Huy Hoang Available at: https://www.tutorialsteacher.com/core/dotnet-core [Accessed 10 October 2022] Visual Paradigm, 2022 Visual Paradigm Product Overview [Online] Available at: https://www.visual paradigm.com/support/documents/vpuserguide/12/13/5963_visualparadi.html [Accessed 10 October 2022] Visual Paradigm, 2022 What is Entity Relationship Diagram (ERD)? [Online] Available at: https://www.visual-paradigm.com/guide/data-modeling/what-is-entity-relationship-diagram/ [Accessed 10 OCtober 2022] Zola, A., 2022 Bootstrap [Online] Available at: https://www.techtarget.com/whatis/definition/bootstrap [Accessed 10 October 2022] abubakarbilal, 2021 Comparing Best UML Diagram Tools Jose, D., 2021 Backend Frameworks in 2021-22 [Online] Available at: https://www.bridge-global.com/blog/top-backend-frameworks/ Martin, M., 2022 MVC vs MVVM [Online] Available at: https://www.guru99.com/mvc-vs-mvvm.html 92 GCH200739 – Nguyen Huy Hoang Pathak, A., 2022 Best Windows Hosting Platform to Host ASP.NET Applications [Online] Senson, A., 2021 Agile Software Development Methodologies: Which to Choose? Uzayr, S b., 2020 Best Code Editors for Developers 93 GCH200739 – Nguyen Huy Hoang Powered by TCPDF (www.tcpdf.org) Index of comments 3.1 Based on the actual presentation and the report, the student presents parts: SRS document, analyze requirements (customer, store owner, admin), design designs with explanation such as use case, wireflow ; risk matrix assessment ; evaluate technologies, tools and models to develop web application; analyse a business-related problem using appropriate methods and produce a well-structured Software Design Document that defines a proposed solution and includes relevant details on requirements, system analysis, system design, coding, testing and implementation; Compare the differences between the various software development tools and techniques researched and justify your preferred selection as well as your preferred software development methodology (test plan, Draw IO, Gliffy, UML, Rider, Visual Studio, Bootstrap, Python/ Django, ASP Net, Node, IIS, SQL Server , Azure, Hostings, MVC vs MVVM, SDLC, List methodologies, Scrum vs Waterfall ) The student needs to evaluate more about the selection of tools and techniques P1,P2,P3, M1, M2 manhdd Powered by TCPDF (www.tcpdf.org)