Scribd
Upload
36 views4 pages

4

Uploaded by

Kushal Bajracharya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
36 views4 pages

4

Uploaded by

Kushal Bajracharya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1.

Introduction

1.1. Introduction

Web-based apps are a form of program that allows users connect with a remote server via a web
browser. They've exploded in terms of popularity, displacing desktop apps and establishing themselves
as a critical tool for small and large companies all over the world. Standard desktop apps offer various
advantages over web-based apps, the much more significant of which being accessibility. When using
web-based apps, users need not introduce extra code, and programmers do not need to write numerous
version of the same program for multiple operating systems. Any gadget that really can run compatible
browsers and has an active Internet access can use web applications. A client-server software is what a
web application is. It has both a client-side and a server-side component. The word "clients" relates to
the software that is used to operate the software by the person. It's component of a windows
environment, in which multiple computers share data. In the particular instance of a database, for
example, the client is the program that the user uses to enter data. The information is stored on the
server, which is an application.

1.2. Objectives
 Give the event organizer a place to stay.
 Ensure that participants who attend the event's knowledge is maintained
 Make the customer's experience as pleasant as possible.
2. Requirement Gathering
Needs extraction (also known as Requirements Gathering or Capturing) is the procedure of getting a set
of demands (functional, systems, technological, and so on) from diverse participants (clients, users,
suppliers, IT employees, and so on) to be used as the foundation for mandatory Requirements. The
approach is more complicated than just asking stakeholder whatever they want their system to perform
because, in many situations, they are unaware of all the options available and may be limited by their
present state of absorption. There are two types of requirements classifications:

1. Functional Requirements
The basic network behavior can be defined by functional requirements. They can be did think of
as where the framework behaves to inputs, because they are largely what the framework will or
will not do in reaction to inputs. Estimates, data input, and business operations are regularly
included in requirement specification, which define if/then actions.
2. Non-functional requirements
Extensibility and achievement. What is the system's response time? How much will this
achievement change as workloads increase?
Suitability and flexibility. What hardware, software platforms, and web browser does the
software support, as well as their variants? Is it incompatible with other applications in these
settings?
Stability, scalability, and supportability are all important factors. How often do critical failures
can occur in the system? However much time is it provided to users in the event of a leisure
time?
Security. What safeguards are in place to protect the network and its information against cyber-
attacks?

Translation. Is the system tailored to the needs of the local community?

Accessibility. How simple is the system to use for a customer?


3. Architecture design
Model-View-Controller is an acronyms for Model-View-Controller. People can interact and engage via
the web, as seen in the diagram above. A database statement is a statement of an entity in the database
(M). Obtaining the data and entering it into a database is crucial. The controller determines the data
retrieval and processing methodology or operations to be used (C). The term assigned to the page that
displays on the computer is called the View (V). In the global routing, all of the components that must be
delivered are presented. All of the program's functions are controlled and maintained by the controller.

3.1. Entity Relationship diagram


4. Screenshots
1. Home page

Conclusion
This architecture was approved using the ASP.NET MVC framework. At the conclusion of this procedure,
we look at the organization and function of the MVC framework. This research also allowed us to quickly
integrate what we'd learned and create an event management accurate measure of event coordinators,
attendees, and people who have attended or are planning to attend activities.

You might also like