Economical Feasibility

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

ECONOMICAL FEASIBILITY

This study's objective is to assess the system's possible financial impact on the business. The
company can only invest so much money in system research and development. The expenses
must be justified. The designed system could also be put into use within the budgetary
constraints because most of the technologies used were freely accessible. The customized
goods were all that needed to be provided.

TECHNICAL FEASIBILITY

This examination is being conducted in order to determine the technical requirements or


viability of the system. Any gadget that is developed should no longer place a significant
strain on the technical resources that are accessible. High standards will ultimately be met for
the technically attainable assets. The buyer will therefore have to adhere to stringent
standards. The developed gadget must have modest requirements because its deployment will
require minimal or no changes at all.

SOCIAL FEASIBILITY

One of the goals of the study is to assess the machine's degree of consumer acceptability. This
means teaching the customer how to use the era efficiently through coaching. Instead of being
perceived by the consumer as a threat, the item should be well-liked. The methods employed
to acquaint and instruct users about the system will dictate the degree of acceptance among
them. Being the last person to utilize the system, he should feel more comfortable offering
some insightful criticism that is greatly valued.

3.6 VISUAL MODELING:

3.6.1 UML DIAGRAMS:

Why We Use UML in projects?

The software industry is searching for ways to automate software creation, enhance
quality, lower costs, and shorten time-to-market as software's strategic importance to many
businesses grows. Patterns, frameworks, visual programming, and component technology
are some of these methods. Companies are also looking for ways to control the complexity
of systems as they grow in size and scope. They understand the necessity to provide
solutions for reoccurring architectural issues including load balancing, fault tolerance,
security, concurrency, and physical distribution. Furthermore, these architectural issues
have been made worse by the emergence of the World Wide Web, despite certain aspects
being made simpler. To meet these objectives, the Unified Modelling Language (UML) was
created. Systems design, put simply, is the act of specifying the architecture, parts, modules,
interfaces, and data for a system in order to meet predetermined requirements. This may be
accomplished with ease using UML diagrams. Three fundamental UML diagrams from the
following list have been explained in the project:
 Class diagram
 Sequence Diagram
 Use Case Diagram
 Data Flow Diagram
CLASS DIAGRAM
A class diagram in software engineering is a form of static structure diagram that shows the
classes, attributes, and interactions between the classes in a system. It is created using the
Unified Modelling Language (UML).
Service Provider

Methods

Members

Login
Register

Methods Methods

Members Members

Remote User

Methods

Members

Fig.8 Class Diagram

Among the diagrams in development, this is one of the most significant. The class is
divided into three layers in the illustration. One has the name, the other explains its
qualities, and the third gives its techniques. The private attributes are represented by a
padlock to the left of the name. The connections between the classes are drawn. The Class
Diagram is used by developers to create classes. It is used by analysts to display the
system's details. Class diagrams are used by architects to identify classes that need to be
divided up or if any classes have too many functionalities.
USE CASE DIAGRAM
A use case diagram is a form of behavioural diagram used in software engineering that is
defined by and produced from a use-case study. It is constructed using the Unified Modeling
Language (UML).

Service
Provider
Remote User

Fig.9 Use Case Diagram

Its objective is to provide a graphical summary of the functionality that a system offers in
terms of actors, use cases (representations of their goals), and any interdependencies among
those use cases. A use case diagram's primary goal is to display which actors receive which
system functionalities. It is possible to illustrate the roles of the system's actors. Use cases
serve as a representation of the system's functionality during requirements elicitation and
analysis. Use cases concentrate on how the system behaves when viewed from the outside.
The use cases are contained inside the system's boundaries, while the actors are outside it.

SEQUENCE DIAGRAM
In the Unified Modeling Language (UML), a sequence diagram is a type of
interaction diagram that illustrates the relationships and sequence in which processes operate
with one another.

It is a Message Sequence Chart construct. Event-trace diagrams, event situations, and


timing diagrams are other names for sequence diagrams.

REGISTER AND LOGIN

PREDICT MESSAGE TYPE


Login,
VIEW YOUR PROFILE
Train & Test Message Data Sets,

View Trained and Tested Accuracy in Bar


Chart,

View Trained and Tested Accuracy


Results,

View Prediction Of Message Type,

View Message Type Ratio,

Download Predicted Data Sets,

View Message Type Ratio Results,

View All Remote Users

Fig.10 Sequence Diagram


DATA FLOW DIAGRAM
1. Another illustration of a DFD call is a bubble chart. A system can be represented
using this straightforward graphical formalism in terms of the input data it receives,
the various operations it does on that data, and the output data it generates.
2. One of the most important modeling instruments is the data accompanying the drift
diagram (DFD). It is employed to model the various components of the system. These
components consist of the information flows stored in the system, the way it
functions, the data it uses, and a third party that interacts with it.
3. DFD illustrates the flow of information through the system and the various changes
that alter it. This method uses graphics to show how information flows and the
changes made to data as it goes from input to output.
4. Another name for DFD is a bubble chart. Any level of abstraction can be utilized to
portray a system using a DFD. DFD can be divided into phases that correspond to
escalating functional detail and information flow.

Train & Test User Profile Data Sets, View


User Profile Trained and Tested Accuracy
in Bar Chart, View User Profile Trained
and Tested Accuracy Results,

Service Provider Login


System PREDICT PROFILE
IDENTIFICATION
STATUS,

View All Profile Identity Response


Prediction, Find and View Profile Register and
Identity Prediction Ratio, View Login with the
User Profile Identity Ratio VIEW YOUR
system
Results, PROFILE

Request

Download Predicted Data Sets, View Remote User


All Remote Users
Tweet Server

Tweet Server

Fig.11 Data Flow Diagram

You might also like