A SYNOPSIS ON

“Self Designed Graphical Invites”

Submitted in partial fulfillment of the requirements

for the award of the degree of

BACHELOR OF COMPUTER APPLICATIONS

To

Guru Gobind Singh Indraprastha University, Delhi

Under the Guidance of: Submitted by:

Dr. Mukta Sharma SHRUTI (03324002019)

Assistant Professor RITIK(01824002019)
BCA-V Semester

Session 2019 – 2022

TRINITY INSTITUTE OF PROFESSIONAL STUDIES

(Affiliated to Guru Gobind Singh Indraprastha University, Delhi)
Ranked “A+” Institution by SFRC, Govt. of NCT of India
Recognized under section 2(f) of the UGC Act, 1956
NAAC Accredited “B++” Grade Institution
 TRINITY INSTITUTE OF PROFESSIONAL STUDIES
(Affiliated to Guru Gobind Singh Indraprastha University, Delhi)
Ranked “A+” Institution by SFRC, Govt. of NCT of India
Recognized under section 2(f) of the UGC Act, 1956
NAAC Accredited “B++” Grade Institution

To Whom It May Concern

I SHRUTI & RITIK , Enrolment No. 03324002019 & 01824002019 from BCA-
V Sem of the Trinity Institute of Professional Studies, Delhi hereby declare that the
Minor Project Report entitled “Self Designed Graphical Invites” at TRINITY
INSTITUTE OF PROFESSIONAL STUDIES is an original work and the same
has not been submitted to any other Institute for the award of any other degree.

Date: Shruti & Ritik

Certified that the Project Report submitted in partial fulfilment of Bachelor of

Computer Applications (BCA) to be awarded by G.G.S.I.P. University, Delhi by
SHRUTI & RITIK, Enrolment No. 03324002019 & 01824002019 has been
completed under my guidance and is Satisfactory.

Date: Signature of the Guide

Dr. MUKTA SHARMA

ASSISTANT PROFESSOR
 CONTENTS

S No Topic Page No
1. Introduction: Problem definition
2. Methodology
3. Tools: Software and Hardware Requirement
4. Systems Design-ER diagram/DFD
5. Future Scope
6. Conclusion
7. References
 INTRODUCTION
In the visual world of technology, where everyone is busy in their own lives and don’t even have
time to meet all their known. Unlike earlier times, when people used to visit each other’s place to
invite them for their happy moments, etc.
So to make things more easier, we have designed a website named “VOWSY INVITES”.
In Vowsy invites, we offer our users various kinds of elegant graphical cards like wedding cards,
birthday cards, ceremony cards, business cards, etc., which has some perks.
Firstly, our users will have multitude options of cards and its design. Secondly, the cards will be
easy to download.
Unique thing about our website is that, all the cards will be self-designed by us and hence will
not be available on portals like Google or any other website. Non-plagiarized invites are
guaranteed.
Through these virtual invites, people can find the most economic friendly invites with
munch self-choice. This new business pattern can save a lot of time and energy for both
customers and manufacturers, and greatly reduce inventory risk. The design of invites
can be produced and procure according to customer needs, and this was called on-
demand production and procurement which greatly improved the efficiency.
Vowsy Invites is a Web-Based Online Project. It is the graphical user interface. It has a
form for user to input query information regarding their choices.

Scope of the Project

‘Change is the only constant’ is a popular saying which is unquestionably true. There was a time
when traditional wedding cards were a must to invite guests to a wedding. These cards were
handwritten and depicted the importance of the event. Later, printed cards came into being and
replaced hand-written cards that took a lot of wedding preparation time. And now, we have
digital cards that can be mailed easily to the invitees and can save a lot of time and money.

There are a huge number of benefits that digital cards offer to the host of the event as well as to
the invitees, including –

 They are Eco-friendly – Going digital with wedding invitations is a very kind thing
we can do for the environment. A lot of paper is used in the traditional wedding invitations.
Going paperless saves trees and in turn, the planet. To give away the printed cards, people
travel. This consumes a lot of fuel and contribute to pollution. Sending digital cards
through email saves a lot of fuel and energy. No waste is generated due to wedding
stationary’s throwing away when we go digital with the cards. Digital Invitations are
surely an environment saving bonanza.
 Money Saving – Digital cards are comparatively more economical than printed cards.
There is a considerable cost difference in the two that can help save a small fortune of the
event organisers.

Not only is the cost saved directly, but even indirectly a lot of money is saved. Digital
cards mean no postal charges and no fuel consumption and thus, quite a lot of saving is
done, that can be utilized in many important wedding preparations.

 Quicker and Easier – Digital cards get prepared in just a few days and can be sent
away with just one click. This saves a lot of time and therefore, is a great option for those
who do not have much time for the wedding preparations. The left over time can be
utilized for other important work. One click and all the guests you selected will receive the
invitation in no time.

 Easy Management of Food and Space – Digital invitation cards offer many
interesting features. For the host of the event, it gets very peaceful if they know how many
people are going to attend. It helps them manage the space and food accordingly. Digital
cards make RSVP more simplified. The invitees can simply reply back on the invitation by
filling in the RSVP form and sending it to the event host.

These are the many reasons why digital cards are getting more and more popular these days.
They clearly offer many advantages with little or no disadvantage comparatively. Digitalization
can be the future of invitations that can have a huge impact on the world.

Objectives of the project

Starting the project, we should fully know about the meaning of project. There are
seven letters in the word “PROJECT”. Each character has its own technical meaning.
P – Planning: this deals with the idea at thinking and which are required for project.
R – Resource: the money problem will be solved and resources from which collected.
O – Operating: the procedure from which getting job is prepared in a systematic way is
known as operation.
J – Joint effort: this is directly proper to a operation output is a made of several person
working sincerely is known as JOIN EFFORT.
E – Engineering: A well-educated engineer can do this work in a better way to find out
better result. Hence the project is as engineer function.
C – Cooperation: To make the project successfully, it is necessary for its success and
completion of project.
T – Technique: It must as it gives a better shape. It is not possible to complete the project
 without technique.
The project is a system that gives the systematic way of planning and working.
Or
It representing the temporary task, in a scientific manner carried out of engineers to
achieve.

NUMBER OF MODULES

After careful analysis the system has been identified to have the following modules:

DASHBOARD

In this user can Briefly view expenses on: -

• Home
• Categories
• About Us
• Contact Us
HOME

In this field, user can view pre-ready samples of the invites in all the categories.

Along-with Subscribe and Feedback options.

CATEGORIES
In this action, user can choose which-ever type of invites they want. The main functions
of the users are:

• Choose Invite Type & download

• Wedding invites

• Business cards

• Birthday invites, etc., are available in varied collection.

FEEDBACK

In this section, user can write good/bad reviews to the admin.

This includes: -
• Name
 • Designation
• Email
• Star ratings
• Message

ABOUT US

In this section user can view the designer details and motive behind making the website.

SUBSCRIBE

In this section, user can subscribe to our website and get regular updates about our new invites
through email.
This includes: -
• User-Name
• Email

CONTACT US

In this section, user can send opinions or details about their personalized invites.
This includes: -
• First Name
• Last Name
• Contact
• Designation
• Email
• Message
METHODOLOGY
An effective System Development Life Cycle (SDLC) should result in a high
quality system that meets customer expectations, reaches completion within time
and cost evaluations, and works effectively and efficiently in the current and
planned Information Technology infrastructure.
System Development Life Cycle (SDLC) is a conceptual model which includes policies and
procedures for developing or altering systems throughout their life cycles.
SDLC is used by analysts to develop an information system. SDLC includes the following
activities −

• Requirements
• Design
• Implementation
• Testing
• Deployment
• Operations
• Maintenance

Phases of SDLC

Systems Development Life Cycle is a systematic approach which explicitly breaks

down the work into phases that are required to implement either new or modified
Information System.
 Figure 5.1: Phase of SDLC

Feasibility Study or Planning

• Define the problem and scope of existing system.

• Overview the new system and determine its objectives.

• Confirm project feasibility and produce the project Schedule.
• During this phase, threats, constraints, integration and security of system are also
considered.
• A feasibility report for the entire project is created at the end of this phase.

Analysis and Specification

• Gather, analysis, and validate the information.

• Define the requirements and prototypes for new system.
• Evaluate the alternatives and prioritize the requirements.
• Examine the information needs of end-user and enhances the system goal.
• A Software Requirement Specification (SRS) document, which specifies the software,
hardware, functional, and network requirements of the system is prepared at the end of
this phase.
System Design

• Includes the design of application, network, databases, user interfaces, and system
interfaces.
• Transform the SRS document into logical structure, which contains detailed and
complete set of specifications that can be implemented in a programming language.
• Create a contingency, training, maintenance, and operation plan.
• Review the proposed design. Ensure that the final design must meet the requirements
stated in SRS document.

Finally, prepare a design document which will be used during next phases.

Implementation

• Implement the design into source code through coding.

• Combine all the modules together into training environment that detects errors and
defects.
• A test report which contains errors is prepared through test plan that includes test
related tasks such as test case generation, testing criteria, and resource allocation for
testing.
• Integrate the information system into its environment and install the new system.

Maintenance/Support

• Include all the activities such as phone support or physical on-site support for users
that is required once the system is installing.
• Implement the changes that software might undergo over a period of time, or
implement any new requirements after the software is deployed at the customer
location.
• It also includes handling the residual errors and resolve any issues that may exist in
the system even after the testing phase.
• Maintenance and support may be needed for a longer time for large systems and for a
short time for smaller systems.
DATA FLOW DIAGRAM
A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an
information system. A DFD is often used as a preliminary step to create an overview of the
system.
DFDs can also be used for the visualization of data processing (structured design).

A DFD shows what kind of information will be input to and output from the system,
where the data will come from and go to, and where the data will be stored. It does
not show information about the timing of process or information about whether
processes will operate in sequence or in parallel.

HISTORY

Data flow diagrams were proposed by Larry Constantine. The original developer of
structured design, based on Martin and Estrin's "Data Flow Graph" model of
computation. Starting in the 1970s, data flow diagrams (DFD) became a popular
way to visualize the major steps and data involved in software system processes.
DFDs were usually used to show data flows in a computer system, although they
could in theory be applied to business process modelling. DFD were useful to
document the major data flows or to explore a new high-level design in terms of data
flow.

Data flow diagram Symbols:

External entities: rectangular box

Data flow: arrow headed lines

Process/ function: bubble/ circle.

Data store: narrow opened rectangle.

Types of data flow diagram:

There are two types of data flow diagrams, namely physical data flow diagrams and
logical data flow diagram and it is important to difference between the two:

Physical data flow diagram:

An implementation dependent view of the current system, showing what tasks are carried
out and how they are performed. Physical characteristic can include:

 Names of people.
 Form and document name and number.
 Name of departments.
 Master and transaction files.
 Equipment and device used.
 Locations.
 Names of procedures.
LOGICAL DATA FLOW DIAGRAM:

An implementation independent view of the system, focusing on the flow of data

between processes without regard for the specific devices, storage location or people
in the system. The physical characteristics listed above for physical data flow
diagram will not be specified.

RULES FOR DFD:

• Fix the scope of the system by means of context diagrams.
• Organize the DFD so that the main sequence of the actions reads left to
right and top to bottom.
• Identify all inputs and outputs.
• Identify and label each process internal to the system with rounded
circles.
• A process is required for all the data transformation and transfers.
Therefore, never connect a data store to a data source or the destinations
or another data store with just a data flow arrow.
• Do not indicate hardware and ignore control information.
• Make sure the names of the processes accurately convey everything the
process is done.
• There must not be unnamed process.
• Indicate external sources and destinations of the data, with squares.
• Number each occurrence of repeated external entities.
• Identify all data flows for each process step, except simple Record
retrievals.
• Label data flow on each arrow.
• Use details flow on each arrow.
• Use the details flow arrow to indicate data movements.
• There can’t be unnamed data flow.
• A data flow can’t connect two external entities.
 LEVELS OF DFD:

The complexity of the business system means that it is a responsible to represent the
operations of any system of single data flow diagram. At the top level, an Overview
of the different systems in an organization is shown by the way of context analysis
diagram. When exploded into DFD, they are represented by:
• LEVEL-0: SYSTEM INPUT/OUTPUT
• LEVEL-1: SUBSYSTEM LEVEL DATAFLOW FUNCTIONAL
• LEVEL-2: FILE LEVEL DETAIL DATA FLOW.
The input and output data shown should be consistent from one level to the next.

LEVEL-0: SYSTEM INPUT/OUTPUT LEVEL

A level-0 DFD describes the system-wide boundaries, dealing inputs to and outputs
from the system and major processes. This diagram is similar to the combined user-
level context diagram.

LEVEL-1: SUBSYSTEM LEVEL DATA FLOW

A level-1 DFD describes the next level of details within the system, detailing the data flows
between subsystems, which make-up the whole.

LEVEL-2: FILE LEVEL DETAIL DATA FLOW

All the projects are feasible given unlimited resources and infinite time. It is both
necessary and prudent to evaluate the feasibility of the project at the earliest possible
time. Feasibility and the risk analysis are pertained in many ways. If project risk is
great

LEVEL ‘0’ DFD

LEVEL ‘1’ DFD

LEVEL ‘2’ DFD

Use Case Diagrams User

Dashboard

Subscribe

Choose &
download

Give
Ratings

Give Feedback

Suggest/Personalize
Designs
ER DIAGRAM
Entity Relationship Diagrams are a major data modelling tool and will help organize
the data in your project into entities and define the relationships between the entities.
This process has proved to enable the analyst to produce a good database structure
so that the data can be stored and retrieved in a most efficient manner.

Entity
A data entity is anything real or abstract about which we want to store data. Entity
types fall into five classes: roles, events, locations, tangible things or concepts. E.g.
employee, payment, campus, book. Specific examples of an entity are called
instances. E.g. the employee John Jones, Mary Smith's payment, etc.

Relationship
A data relationship is a natural association that exists between one or more entities.
E.g. Employees process payments. Attribute
A data attribute is a characteristic common to all or most instances of a particular
entity. Synonyms include property, data element, field. E.g. Name, address,
Employee Number, pay rate are all attributes of the entity employee. An attribute or
combination of attributes that uniquely identifies one and only one instance of an
entity is called a primary key or identifier. E.g. Employee Number is a primary key
for Employee.
 E-R DIAGRAM

An entity–relationship model (or ER model) describes interrelated things of interest

in a specific domain of knowledge. A basic ER model is composed of entity types
(which classify the things of interest) and specifies relationships that can exist
between entities (instances of those entity types).
An ER model is typically implemented as a database. In a simple relational database
implementation, each row of a table represents one instance of an entity type, and
each field in a table represents an attribute type. In a relational database a
relationship between entities is implemented by storing the primary key of one entity
as a pointer or "foreign key" in the table of another entity
ER DIAGRAM
 FUTURE SCOPE

The website can be developed to an android / iOS Application. And the online free portal for
DOWNLOADING
graphical invites can have a payment category for premium designs. Adding web security to our
website or application will be our main concern in future.