Documente Academic
Documente Profesional
Documente Cultură
Management System
1. Introduction
2. System Analysis
Operational feasibility
Since the user presumed to use this system are qualified so it is believed that they
have proper knowledge of computers and Internet and hence they will be able to operate
it in a fair manner.
Economical feasibility
Since we assume that the network on which our system will operate will be support
TCP/IP protocol, hence the software needed are mainly C#. NET webserver1.1 and the
Internet Explorer, which can be got very easily
Technical feasibility
As mentioned before the organization is assumed to have well equipped technical
persons who are capable of operating the system also have necessary hardware and can
download the software from the internet. Hence proposed solution is technical feasible.
3. SYSTEM DESIGN
3.2 Hardware and Software Requirements
Software requirements:
Database: MS SQL Server2000 with Microsoft SQL Desktop Engine (MSDE) installed.
.
Framework: NET Framework Version (1.1 only).
Hardware Requirements:
1. Pentium or AMD processors with speed minimum 1GHz.
2. Minimum256MB RAM.
3. Accelerated Graphics Card.
4. Minimum 2GB Hard Disk.
5. Better performance with 82KB and above Cache Memory.
Arrangers
Planning Advertisement
Income
electronic media
resources
Actual event
Response
planning v/s
result comparision
Event No
Date
Nam
Area
e
Venue
Event
Type Event No
Others Addres
s
Responsibility
Deadlin
Charge ess Role
Expenditur s
e Arrangers Employee
Event No
Statemen
t Ph
Role
Physical Sl #
Charges
Expenditure No Consultants
Statemen
t
Event Respons Phone#
no e Name
Date Address
Media Event
Date occurred
Date Detail
Amount
s
Duratio
n
Payment
Department of Computer Science,
7
Event
Management System
Event
No Type
Event
Data type Key attribute
Event No Int PRIMARY
Event Name Varchar
Date Datetime
Event Type Varchar
Expenditure
Physical expenditure
Venue
Arrangers
Employee
Consultants
Event occurred
Payment
Data type Key attribute
Event no Int FOREIGN
Date Date time
Amount Varchar
Type Varchar
Advertising
4. System Implementation
Introduction to .Net
. NET (dot-net) is the name Microsoft gives to its general vision of the future of
computing, the view being of a world in which many applications
run in a distributed manner across the Internet. We can identify a
number of different motivations driving this vision.
At the development end of the .NET vision is the .NET framework. This
contains the common language runtime; the common language runtime (CLR)
manages the execution of code compiled for the .NET platform. The CLR has two
interesting features. Firstly, its specification has been opened up so that it can be
ported to non-windows platforms. Secondly, any number of different languages
can be used to manipulate the .NET framework classes, and the CLR will support
them. This has led one commentator to claim that under. NET the language one
uses is a ‘lifestyle choice’.
Not all of the supported languages fit entirely neatly into the .NET
framework, however (in some cases the fit has been somewhat procrustean). But
the one language that is guaranteed to fit in perfectly is C#. This new language, a
successor to C++, has been released in conjunction with the .NET framework,
and is likely to be the language of choice for many developers working on .NET
applications.
Introduction to C#
C# is a modern, object oriented language that enables programmers to quickly
build a wide range of applications for the new Microsoft .NET platform, which
provides tools & services that fully exploit both computing & communication.
Because of its elegant object oriented design .C# is a great choice for
architecting a wide range of components from high level business objects to
system level applications using simple C# language constructs, these component
can be converted into XML web services, allowing them to be invoked across the
internet, from any language running on any operating system. More than any
thing else, C# is designed to bring rapid development to the C++ programmer
without sacrificing the power & control that have been a hallmark of C & C++.
3.2.2 C# Features
C# is the new language with the power of C++ & the slickness of visual basic. It
cleans up many of the syntactic peculiarities of C++ without diluting much of its
flavor (thereby enabling C++ developers to transition to it with little difficulty). And
its superiority over VB6 in facilitating powerful OO implementation is without
question. C# with clean OO syntax & large class library (in conjunction with .NET
& the base class libraries) could be the ‘most productive mainstream language’ &
it is an ECMA standard language that offers the potential of being available
across many platform .For the serious developer wanting Microsoft’s most
productive & mainstream .NET language, C# is the choice.
Properties:
Properties will be a familiar concept to Delphi & Visual basic users. The
motivation is for the language to formalize the concept of getter/ setter methods,
which is an extensively used pattern, particularly in RAD (Rapid Application
developments) tools.
This is a typical code you must write in Java or C++:
Outsize (get size () +1);
Label.getfont (). Set bold (true);
The same code you would rite like this in C#:
Outsize;
Label.font.bold=true;
The code is immediately more readable by those who are using foot & label.
There is similar simplicity when implementing properties:
Indexers:
C# provides indexers allow objects to be treated like array, except that like
properties, each element is exposed with a get and/ or set method.
Delegates:
Events:
C# provides direct support for events Although event handling has been a
fundamental part of programming since programming began, there has been
surprisingly little efforts made by most languages to formalize this concept, If you
look at how today’s mainstream frameworks handle events. We’ve got examples
like Delphi’s function pointers (called closures), Java’s inner class adapters & of
course, the windows API’s message system. C# uses delegates along with the
event keyword to provide a very clean solution to event handling .I thought the
best way to illustrate this was to give an example showing the whole process of
declaring, firing & handling an event.
Pointer arithmetic:
Rectangular Arrays:
C# allows both jagged & rectangular arrays to be created. Jagged arrays are
pretty much the same as Java arrays. Rectangular arrays allow a more efficient
and accurate representation for certain problems .An example of such an array
would be:
Int [,] array = new int [3,4,5];
Int [1][1][1];
In combination with struts, C# can provide a level of efficiency making it a good
choice for areas such as graphics & mathematics.
A sample C# program:
Hello world
File Hello .Cs
Using system;
Class Hello {
Static void Main (){
Console. Write Line (“Hello world “);
}
}
Uses the namespace System
Entry point must be called Main
O/p goes to the console
File name & class name need not be identical
Compilation (in the console window)
Csc Hellow .cs
Execution
Hello
C# Advantages:
C# Applications:
5. Testing
B. V-model:
CODING TEST
CASES
TESTING
PHASE
MAINTAINANCE
PHASE
It is same as waterfall model but difference is that testing and development are
SOFTWARE TESTING
What is testing?
Since the software can perform 100,000 correct operations per second, it
has the same ability to perform 100,000 wrong operations per second, if not
tested properly.
White Box Testing: The software tester has SQL Server 2000 to the
program/code and examines it for errors. Also called clear box testing or
Black Box Testing: The software tester only knows what the system is
supposed to do; he does not know how it works internally. He has to test on
Automated Testing: Testing activities carried out with the help of software
Validation: Is a set activities carried out to check whether we are ‘building the
right system’.
2. Design testing
3. Unit testing
4. Integration testing
5. System testing.
as the errors noticed at the end of the software life cycle are more costly
compared to that of early ones, and there by validating each of the outputs.
Correctness
Consistency
B. Design Testing
a) Consistency
b) Completeness
c) Correctness
d) Feasibility
e) Trace ability
C. Unit Testing
Objective: The main objective of unit testing is to ensure that the individual units
a) Correctness
b) Completeness
c) Early testing
d) Debugging
D. Integration testing
errors.
E. Software Testing
verified for proper interface with other system elements like hardware, databases
and people.
System testing verifies that all these system elements mesh properly and
We carry out functionality testing, performance testing and other black box
- Unit Testing
- Integration testing
- Functional testing
- System testing
- Acceptance testing
- Regression testing
- Performance testing
- Security testing
Reviews: A group of persons (author need not be one among them) look for
members of the group which will include the author. For E.g.: Improving
Unit testing: Testing a single program, module, or unit of code. Validates that
testing.
Validates that multiple parts of the system interact according to the system
design.
Functional testing: Functions are tested by feeding the input and examining
the output to the expected outputs. Functional tests are a type of black box
testing.
System Testing: Testing of entire system can include functional and non-
have not caused unintended adverse effects. To verify that a modified system
Usability Testing: Evaluates the ease of using and learning the system and
system functioning in supporting user tasks and ability to recover from user’s
errors.
- Configuration Testing
- Installation Testing
- Load Testing
5. Test reports.
Design requirements
1. Its specification
2. Functional requirements
3. Functional specification
After these two processes step is to run the type of application tested
Bug tracking mechanism is one in which the bug /errors are traced.
e. Test Reports:
MANUAL TESTING
Writing the test cases does manual testing. Here, test case is defined as
writing the sequence of messages. Manual tester writes the test cases. After a
test case has been written for particular application then these test cases are
executed. It consists of actual result, expected result and the respected status of
the application. If that application is bug free then status is said to be passed.
Else if any application then it should be understood that it should be tested again.
Testing
approved or accepted. The test cases that were considered for the project
were
i) User leaving a blank field: In all the forms validation rules are used
fields. Whenever the user leaves a field blank the form doesn’t get
submitted.
ii) User trying inserting ambigues values in the foreign keys: the
system is meant to help the users to link the primary and the
secondary data. Hence if the user inserts wrong key value he will
user can manipulate with the date and thus it may cause a huge
iv) All the pages are secured: all the pages were needed to provide
6. Future Enhancement
The event management system is a means of appropriately handling and managing the
events and all the related and the associated data. The system can be made online in
future to maintain all the global events. No cost estimation is included in the current
module. In future cost estimation module can be integrated along with the fuzzy based
technique through which the costs of an new event can be judged from the existing events
from the database.
7. Conclusion
The event management system used over here is implemented in .Net platform, which is
a next generation solution for all the Microsoft related products. Therefore the solution is
futuristic. It is been tested manually for all the possible test cases. Hence the system is a
reliable and stable system. The reports are easier to use and import and the solution can
easily be integrated with the Internet. The project is an attempt to provide a prototype for
what an event management system can be! Therefore more commercial aspects are
needed to be validated for the system to be a commercially viable one.
9. Bibliography
namespace Event_Management_System
{
/// <summary>
/// Summary description for PhysicalExpenditure.
/// </summary>
public class PhysicalExpenditure : System.Windows.Forms.Form
{
private System.Windows.Forms.Label label1;
private System.Windows.Forms.Label label2;
private System.Windows.Forms.Label label3;
private System.Windows.Forms.Label label4;
private System.Windows.Forms.GroupBox groupBox1;
private System.Windows.Forms.DataGrid dataGrid1;
private System.Windows.Forms.Button btnsubmit;
private System.Windows.Forms.Button btnviewall;
private System.Windows.Forms.Button btnview;
private System.Windows.Forms.Button btnupdate;
private System.Windows.Forms.Button btndelete;
private System.Windows.Forms.DateTimePicker dtdatetime;
private System.Windows.Forms.TextBox txtstatement;
private System.Windows.Forms.TextBox txteventno;
private System.Windows.Forms.TextBox txtcharges;
/// <summary>
/// Required designer variable.
/// </summary>
private System.ComponentModel.Container components = null;
public PhysicalExpenditure()
{
//
// Required for Windows Form Designer support
//
InitializeComponent();
//
// TODO: Add any constructor code after InitializeComponent call
//
}
}
#endregion
#region
// Insert page code here
//
return rowsAffected;
}
#endregion
private void button1_Click(object sender, System.EventArgs e)
{
int
i=MyInsertMethod(int.Parse(txteventno.Text),DateTime.Parse(dtdatetime.Text),int.Parse(
txtcharges.Text),txtstatement.Text);
if(i>0)
MessageBox.Show("Submitted successfully");
else
MessageBox.Show("Failed to Submit");
}
#region
System.Data.DataSet MyQueryMethod()
{
string connectionString = "server=\'(local)\';
trusted_connection=true; database=\'user1\'";
System.Data.IDbConnection dbConnection = new
System.Data.SqlClient.SqlConnection(connectionString);
return dataSet;
#endregion
private void btnviewall_Click(object sender, System.EventArgs e)
{
dataGrid1.DataSource=MyQueryMethod();
dataGrid1.Expand(-1);
}
#region
return dataSet;
}
#endregion
private void btnview_Click(object sender, System.EventArgs e)
{
dataGrid1.DataSource=MyQueryMethod(int.Parse(txteventno.Text));
}
#region
int rowsAffected = 0;
dbConnection.Open();
try
{
rowsAffected = dbCommand.ExecuteNonQuery();
return rowsAffected;
}
#endregion
private void btnupdate_Click(object sender, System.EventArgs e)
{
int
i=MyUpdateMethod(int.Parse(txteventno.Text),DateTime.Parse(dtdatetime.Text),int.Pars
e(txtcharges.Text),txtstatement.Text);
if(i>0)
MessageBox.Show("Updated Successfully");
else
MessageBox.Show("Failed to Update");
}
#region
int rowsAffected = 0;
dbConnection.Open();
try
{
rowsAffected = dbCommand.ExecuteNonQuery();
return rowsAffected;
}
#endregion
private void btndelete_Click(object sender, System.EventArgs e)
{
int i=MyDeleteMethod(int.Parse(txteventno.Text));
if(i>0)
MessageBox.Show("Deleted Successfully");
else
MessageBox.Show("Failed to Delete");
}
}
}