Professional Documents
Culture Documents
SUBMITTED TO
HARPREET SINGH
Reg. No. 10802469
Roll. No. R246A26
TABLE OF CONTANTS
1. Introduction
2. Proposed system
i. Description
ii. System requirements
3. Requirement Analysis
4. System Design
5. Source code
6. Testing
7. Future scope of project
INTRODUCTION
In the existing system, most of the records are maintained on
paper. It becomes very inconvenient to modify the data. In the
existing system, here is a possibility that the same data in different
registers may have different values which means the entries of the
same data do not match. This inconsistent state does not supply the
concrete information which poses a problem in the case
information related to particular search record.
Our project is very useful. User is no longer required to check his
register in search of records, as now it can be searched over the
software by choosing some options. The user need not to type in
most of the information. He/she is just required to enter the desired
options. On the whole it liberates the user from keeping lengthy
manual records. In a nutshell, it abates the work load of an
organization.
In today’s world, no one likes to perform calculations on calculator
or manually when computer is there. Every one wants his/her work
to be done by computer automatically and displaying the result for
further manipulations.
PROPOSED SYSTEM
The following documentation is a project the “Name of the term
paper allotted”. It is a detailed summary of all the drawbacks of the
old system and how the new proposed system overcomes these
shortcomings. The new system takes into account the various
factors while designing a new system. It keeps into the account the
Economical bandwidth available for the new system. The foremost
thing that is taken care of is the Need and Requirements of the
User.
DESCRIPTION
SYSTEM DESIGN
Then we began with the design phase of the system. System design
is a solution, a “HOW TO” approach to the creation of a new
system. It translates system requirements into ways by which they
can be made operational. It is a translational from a user oriented
document to a document oriented programmers. For that, it
provides the understanding and procedural details necessary for the
implementation. Here we use Flowchart to supplement the working
of the new system. The system thus made should be reliable,
durable and above all should have least possible maintenance
costs. It should overcome all the drawbacks of the Old existing
system and most important of all meet the user requirements.
START
WELCOME TO PROGRAM
ENTER
DOB
STOP
SOURCE CODE
#include<stdio.h>
#include<stdlib.h>
#include<conio.h>
main()
{
clrscr();
int d,m,y,year,month,day,i,n;
printf("Enter how many times you want to run this program : ");
scanf("%d",&n);
for(i=1;i<=n;i++)
{
printf("Enter the date : ");
scanf("%d%d%d",&d,&m,&y);
if( d>31 || m>12 || (y>1900 || y<=2000) )
{
printf("INVALID INPUT");
getch();
exit(0);
}
year = y-1900;
year = year/4;
year = year+y-1900;
switch(m)
{
case 1:
case 10:
month = 1;
break;
case 2:
case 3:
case 11:
month = 4;
break;
case 7:
case 4:
month = 0;
break;
case 5:
month = 2;
break;
case 6:
month = 5;
break;
case 8:
month = 3;
break;
case 9:
case 12:
month = 6;
break;
}
year = year+month;
year = year+d;
day = year%7;
switch(day)
{
case 0:
printf("Day is SATURDAY");
break;
case 1:
printf("Day is SUNDAY");
break;
case 2:
printf("Day is MONDAY");
break;
case 3:
printf("Day is TUESDAY");
break;
case 4:
printf("Day is WEDNESDAY");
break;
case 5:
printf("Day is THURSDAY");
break;
case 6:
printf("Day is FRIDAY");
break;
}
}
getch();
return 0;
}
TESTING
Testing is the major control measure used during software
development. Its basic function is to detect errors in the software.
During requirement analysis and design, the output is a document
that is usually textual and no executable. After the coding phase,
computer programs are available that can be executed for testing
purpose. This implies that testing not only, has to uncover errors
introduced during coding, but also errors introduced during
previous phase. Thus the goal of testing is to uncover the
requirements, design and coding errors in the programs. So after
testing the outputs of my project are as follows:
If we use this program in big code program then we can get more
good results than what will we get now? We can use this program
in astrology or if we concentrate more on this project than we can
also find the time of birth from this program.
References:
www.google.com
www.sourcecodeworld.com