Experiment 1: 1. The Web Form-My Calendar Introduction

Experiment 1
1. THE WEB FORM-MY CALENDAR INTRODUCTION

The software program the web form- my calendar is the online calendar ,in which we can assign different events
to the week days and can ever edit that and update it to the main calendar and displays the events that occurs on
any particular date, the events are stored in xml database .The front end used for this project is Asp .Net and the
back end is XML. It provides a good working environment which is easy to learn and use.
2. IDENTIFICATION OF NEED
(a) The application does not provide security to the system.
(b) There is no flexibility to the database.
(c) There is no GUI interaction for more convenience.
(d) Coding is not much efficient.
(e) Most of the work is done manually.
(f) More man power is required, so it is costly.
(g) The redundancy and inconsistency of data is major drawback.
3. PRELIMINARY INVESTIGATION
As the initial investigation is completed, it leads to a more detailed investigation of the system. The
conclusions of the initial study become the input for the detailed study. We can also refer to the feasibility
study as the detailed study or detailed investigation. Feasibility study is called like because as in the first
phase, we just check briefly about the problems related to the old system, & the need of the new system. So,
in this phase, that initial survey is further expanded to a more detailed feasibility study.
The tasks performed during this phase were as follows:

(a) The user.s demonstrable needs are fulfilled.
(b) The availability of resources was being checked.
(c) The estimation required for the resources were achieved.
(d) The impact of the system on the organization has been check by placing a
model in it.
PROPOSED SYSTEM:
Objective To Be Fulfilled:
(a) Development of software in the given time.
(b) To create an effective and efficient application.
Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

User Requirements:
(a) The application should provide a user friendly environment.
(b) The application should be easily understandable and reliable.
(c) The application should fulfill all essential facilities.
(d) The software being built must provide platform independent application.
4. SYSTEM DEVELOPMENT METHODOLOGY

The hardware and software requirement for this project are as follows:
HARDWARE - Hard Disk : 5 GB
RAM : 128 MB
SOFTWARE - Operating System : Windows Family
Asp .Net: As Front End
XML: As Back End

Experiment 2
SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC),or Software Development Life Cycle in

systems engineering, information systems and software engineering, is the process of creating or altering
systems, and the models and methodologies that people use to develop these systems. The concept generally
refers to computer or information systems.
Systems Development Life Cycle (SDLC) is a process used by a systems analyst to develop an information
system, including requirements, validation, training, and user (stakeholder) ownership. Any SDLC should result
in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost
estimates, works effectively and efficiently in the current and planned Information Technologyinfrastructure,
and is inexpensive to maintain and cost-effective to enhance.
The Development Life-Cycle
• A project is a set of activities, interactions and results.

• A life-cycle or a software process is the organisational framework for a project.
Life Cycle
• A life-cycle :
• is a finite and definite period of time.
• starts when a software product is conceived.
• ends when the product is no longer available or effective for use.
• Any life-cycle is organised in (composed of) phases.
Types of SDLC
• More than one possible life cycle can be adopted to attain a particular goal.
• The type of SDLC is defined by the way it links the development phases.
• In theory, any combination of phases is possible, however, in practice only ones that lead to a visible and
controllable development process are useful.
• A type of SDLC is known as a Development Model.
Development Models
• Development model definition (personal): A particular interaction configuration of development

phases leading to a final software product.
• Waterfall (and Enhanced Waterfall)
• V-model
• Evolutionary Prototyping (aka Incremental)

• Throw-away Prototyping (aka Rapid)
• Rapid Application Development (RAD)
• Spiral  Research independently
• Reuse-oriented
A Systems Development Life Cycle (SDLC) adheres to important phases that are essential for developers, such
as planning, analysis, design, and implementation, and are explained in the section below. A number of system
development life cycle (SDLC) models have been created: waterfall, fountain, and spiral build and fix, rapid
prototyping, incremental, and synchronize and stabilize. The oldest of these, and the best known, is the waterfall
model: a sequence of stages in which the output of each stage becomes the input for the next. These stages can
be characterized and divided up in different ways, including the following:
• Project planning, feasibility study: Establishes a high-level view of the intended project and
determines its goals.
• Systems analysis, requirements definition: Refines project goals into defined functions and operation
of the intended application. Analyses end-user information needs.
• Systems design: Describes desired features and operations in detail, including screen layouts, business
rules, process diagrams, pseudo code and other documentation.
• Implementation: The real code is written here.
• Integration and testing: Brings all the pieces together into a special testing environment, then checks
for errors, bugs and interoperability.
• Acceptance, installation, deployment: The final stage of initial development, where the software is put
into production and runs actual business.
• Maintenance: What happens during the rest of the software's life: changes, correction, additions, and
moves to a different computing platform and more. This, the least glamorous and perhaps most
important step of all, goes on seemingly forever.
An SDLC has three primary business objectives:
• Ensure the delivery of high quality systems;

• Provide strong management controls;
• Maximize productivity.
In other words, the SDLC should ensure that we can produce more function, with higher quality, in less time,
with fewer resources and in a predictable manner.

Ensure High Quality
Before we can ensure that a system has high quality, we must know what quality is in a business context.The
primary definition of quality in a business context is the return on investment (ROI)achieved by the system. The
business could have taken the money spent on developingand running the system and spent it on advertising,
product development, staff raises ormany other things. This ROI can be operational cost savings or cost
avoidance; improved product flexibility resulting in a larger market share; and/or improved decision support for
strategic, tactical and operational planning. This definition of quality centres on the characteristics of the system
itself: is it zero defect, is it well-structured, it is well-documented, is it functionally robust, etc. ability to provide
the best possible ROI.
Provide Strong Management Control

The essence of strong management controls is predictability and feedback. Projects maylast for many months or
even years. Predictability is provided by being able to accuratelyestimate, as early as possible, how long a
project will take, how many resources it willrequire and how much it will cost. The SDLC must ensure that such
planning estimates can be put together before there have been any significant expenditures of resources, time
and money on the project. The feedback process tells us how well weare doing in meeting the plan and the
project's objectives. The SDLC must ensure thatmanagement has timely, complete and accurate information on
the status of the projectand the system throughout the development process.

Maximize Productivity
There are two basic definitions of productivity. One centres on what you are building;the other is from the
perspective of how many resources, how much time and how muchmoney it takes to build it. The first definition
of productivity is based on the return oninvestment (ROI) concept. It must ensure that the projects being done
are those with the maximumpossible ROI opportunities of all of the potential projects.The SDLC must be
designed in such a way as to take maximum advantageof the computer assisted software engineering (CASE)
tools.The SDLC mustensure that start-up time is minimized in any way possible. A final opportunity area
forproductivity improvements is the use of off-the-shelf components. Many applications contain functions
identical to those in other applications. The SDLC should ensure that ifuseful components already exist, they
can be re-used in many applications.

Experiment 3
Process: Process Model for the Project.
The waterfall model
• Separate and distinct phases of specification and development
The waterfall model was selected because of the simple design of the project. The entire requirements in the
project were well-defined in the beginning and hence, the waterfall model suited the best with minimum
expenditure on both time and cost.
The stages of "The Waterfall Model" are:

Requirement Analysis & Definition: All possible requirements of the system to be developed are captured in
this phase. Requirements are set of functionalities and constraints that the end-user (who will be using the
system) expects from the system. The requirements are gathered from the end-user by consultation, these
requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to
be development is also studied. Finally, a Requirement Specification document is created which serves the
purpose of guideline for the next phase of the model.
System & Software Design: Before a starting for actual coding, it is highly important to understand what we
are going to create and what it should look like? The requirement specifications from first phase are studied in
this phase and system design is prepared. System Design helps in specifying hardware and system requirements
and also helps in defining overall system architecture. The system design specifications serve as input for the
next phase of the model.
Implementation & Unit Testing: On receiving system design documents, the work is divided in modules/units
and actual coding is started. The system is first developed in small programs called units, which are integrated in
the next phase. Each unit is developed and tested for its functionality; this is referred to as Unit Testing. Unit
testing mainly verifies if the modules/units meet their specifications.
Integration & System Testing: As specified above, the system is first divided in units which are developed and
tested for their functionalities. These units are integrated into a complete system during Integration phase and
tested to check if all modules/units coordinate between each other and the system as a whole behaves as per the
specifications. After successfully testing the software, it is delivered to the customer.
Operations & Maintenance: This phase of "The Waterfall Model" is virtually never ending phase (Very long).
Generally, problems with the system developed (which are not found during the development life cycle) come
up after its practical use starts, so the issues related to the system are solved after deployment of the system. Not
all the problems come in picture directly but they arise time to time and needs to be solved; hence this process is
referred as Maintenance.

Experiment 4
Project Plan
A feasibility study is an evaluation of a proposal designed to determine the difficulty in carrying out a
designated task. Generally, a feasibility study precedes technical development and project implementation. In
other words, a feasibility study is an evaluation or analysis of the potential impact of a proposed project.
Technical Feasibility
In technical feasibility the following issues are taken into consideration.
• Whether the required technology is available or not

• Whether the required resources are available
• Manpower- programmers, testers & debuggers
• Software and hardware
Once the technical feasibility is established, it is important to consider the monetary factors also. Since it might
happen that developing a particular system may be technically possible but it may require huge investments and
benefits may be less. For evaluating this, economic feasibility of the proposed system is carried out.
Economic Feasibility
For any system if the expected benefits equal or exceed the expected costs, the system can be judged to be
economically feasible. In economic feasibility, cost benefit analysis is done in which expected costs and benefits
are evaluated. Economic analysis is used for evaluating the effectiveness of the proposed system. In economic
feasibility, the most important is cost-benefit analysis. As the name suggests, it is an analysis of the costs to be
incurred in the system and benefits derivable out of the system. Click on the link below which will get you to
the page that explains what cost benefit analysis is and how you can perform a cost benefit analysis.
Operational Feasibility
Operational feasibility is mainly concerned with issues like whether the system will be used if it is developed
and implemented. Whether there will be resistance from users that will affect the possible application benefits?
The essential questions that help in testing the operational feasibility of a system are following.
It includes study concerning contracts, liability, violations, and legal other traps frequently unknown to the
technical staff.
The operation of project must not incur any extra resources causing an overhead. Operation must be cost
efficient as well as easily maintainable. The above factors have been well considered and the project is feasible
from operation point of view.
Behavioural Feasibility
The system must be able to handle multiple users simultaneously filling the registration the form. In case of
erroneous input the system must display the problem at the client side.

• Is the audience likely to adopt the behaviour? Is the current behaviour seen as a problem? How
engrained or “rewarding” are the current or competing behaviours?
• How costly is it (time, effort, resources) for the audience segment to perform the behaviour?
• How complex is the behaviour (does it involve few or several elements)?
• How frequently must the behaviour be performed?
• How compatible is the proposed behaviour with the audience’s current practices (is the behaviour
socially approved)?
• Are there major barriers to engaging in the desired behaviour? What information, skills, resources
and/or access must the audience segment acquire to overcome the barriers and make the desired
behaviour change?
• Are there at least some members of the segment (“doers”) who manage to do the desired behaviour? Do
they have unusual characteristics?

Experiment 5
SOFTWARE REQUIREMENTS SPECIFICATION
A Software Requirements Specification (SRS) - a requirements specification for a software system - is a

complete description of the behaviour of a system to be developed. It includes a set of use cases that describe all
the interactions the users will have with the software. Use cases are also known as functional requirements. In
addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional
requirements are requirements which impose constraints on the design or implementation (such as performance
engineering requirements, quality standards, or design constraints).
Software Requirements Specification
For
“THE WEB FORM-MY CALENDAR”
By:
Sparsh Gupta-07CS000061
&
Yadunandan Shrimali-07CS000071
November 21, 2010
Version Changes Made Date
1.0 Not Applicable 28/05/2010

1. Introduction.
1.1 Purpose
The project basically develops a application that allows the user to see the events in the calendar and
can edit them and can add new events that are about to happen.
1.2 Scope
The scope of application is to provide a system which is generalized calendar that can be used for
adding new events and to edit events for that the management of events of the university.
1.3 Abbreviations
Abbreviations are not used here.
2. The Overall Description
2.1 Product Perspective

This product is a event calendar and will be developed on Asp.Net .The system must be good looking
and must be easily updatable.
2.2 Product Function

The event calendar system is a data entry the web-form application that will store data and modify data
and update it to the system.
2.3 User Characteristics

Any user who wants to know the recent event happening in university or wants to modify or add any
event can work on this .
2.4 Constraints
The form has to be developed on windows platform.
2.5 User Interfaces

The Login page should work and be tested against
• Internet Explorer 8
• Firefox 3
2.6 Assumptions and Dependencies.

There are no development assumptions or dependencies.
3. SPECIFIC REQUIREMENTS
3.1 Software Interfaces

There are no special software interface requirements.

Experiment 6
ANALYSIS MODELING
Use Case Diagram:
Use Case diagram is used to identify the primary elements and processes that form the system from the
perspective of user. The primary elements are termed as “actors” and the processes are called “use cases” .The
use case diagram shows which actors interact with each use case. This section describes in detail description of
those diagrams.

ENTITY RELATIONSHIP DIAGRAM:
It represents the object-relationship pairs in graphical forms. Thus, we can say that
the primary goal of E-R diagrams is to represent data objects along with their
relationships.
ER model for data uses three features to describe data:
Entities which specify distinct real world items in an application
Relationships connecting different entities and representing meaningful
dependencies between them.
Attributes which specify various properties of entities and relations involved in a
system.

6.3 DATA FLOW DIAGRAM:
A properly defined flow model diagram, not only helps to understand the working
of the model, but also helps the software designer to built it and test it for validation with ease.
A DFD is a graphical representation that depicts the information flow and the
transforms that are applied as data moves from input to output. It can be used to
represent software at any level of abstraction. In fact, DFD.s may be partitioned
into levels that represent increasing information flow and functional details. The
graphical representation makes it a good tool for communication between designer
and analyst.

Experiment 7
PROJECT DESIGN
Database View

Database View while updating

Experiment 8
PROJECT CODING
<%@ Page Language="c#" %>

<%@ Import Namespace="System.Data"%>
<%@ Import Namespace="System.IO" %>
<%@ Import Namespace="System.Globalization" %>
<html>
<head><title>Event Calendar</title>
<script language="c#" runat="server">
public void MyCalendar_SelectionChanged(object sender, EventArgs e)

{
//This function will be called on selection of any date.
ShowDailyEvents();
}
protected void page_load(object sender, EventArgs e)

{
if (!(Page.IsPostBack))
{
ShowDailyEvents();
}
}
protectedDataSetLoadMyCalendarData()
{
//This function is to load calendar data by connecting to database.
stringsourceXml = Server.MapPath("MyCalendar.xml");
if (!(File.Exists(sourceXml)))
{
return null;
}
DataSetcachedDataSet = (DataSet)Session["MyCalendarData"];
if (cachedDataSet != null)
{
returncachedDataSet;
}
DataSetdataSet = new DataSet();
try
{
dataSet.ReadXml(sourceXml);
Session["MyCalendarData"] = dataSet;
}
catch (Exception e)
{
SelectedDate.Text = e.Message;

dataSet = null;
}
returndataSet;
}
protected void MyCalendar_DayRender(object sender, DayRenderEventArgs e)

{
//This event is raised each time a visible day in the calendar is rendered.
if (e.Day.IsOtherMonth)
{
e.Cell.BackColor=System.Drawing.Color.FromName("Gainsboro");
}
else
{
if (e.Day.IsWeekend)
{
e.Cell.BackColor=System.Drawing.Color.FromName("PaleGoldenrod");
}
else
{
e.Cell.BackColor=System.Drawing.Color.FromName("LightGoldenrodYellow");
}
}
DataSetdataSet = LoadMyCalendarData();
if (dataSet == null)
{
return;
}
foreach (DataRowzRow in dataSet.Tables[0].Rows)
{
DateTimecompareDate = GetSafeDate(zRow["EventDate"].ToString());
if (compareDate == e.Day.Date)
{
// Event matches date criteria – display it...
MyCalendarEventDatamyEventData = new MyCalendarEventData();
myEventData.ShortDesc = zRow["ShortDesc"].ToString();
myEventData.DetailDesc = zRow["DetailDesc"].ToString();
myEventData.StartTime = zRow["StartTime"].ToString();
myEventData.EndTime = zRow["EndTime"].ToString();
Label dailyEventLabel = new Label();
dailyEventLabel.Text = "<br />" + myEventData.ShortDesc;
e.Cell.Controls.Add(dailyEventLabel);
}} }
protected void ShowDailyEvents()
{
//This method has been used to display the detailed information for all
events, based on selected day.
DateTime d = MyCalendar.SelectedDate;

if (dataSet == null)
{
return;
}
ArrayListaEvents = new ArrayList();

foreach (DataRowzRow in dataSet.Tables[0].Rows)
{
DateTimecompareDate = GetSafeDate(zRow["EventDate"].ToString());
if (compareDate == d)
{
// Event matches date criteria – display it...
MyCalendarEventDatamyEventData = new MyCalendarEventData();
myEventData.EventDate = d;
myEventData.ShortDesc = zRow["ShortDesc"].ToString();
myEventData.DetailDesc = zRow["DetailDesc"].ToString();
myEventData.StartTime = zRow["StartTime"].ToString();
myEventData.EndTime = zRow["EndTime"].ToString();
aEvents.Add(myEventData);
}
}
// Bind to the Repeater control...
DailyEventDetailRepeater.DataSource = aEvents;
DailyEventDetailRepeater.DataBind();
if (aEvents.Count> 0)
{
DailyDetailsPanel.Visible = true;
SelectedDate.Text = "Events For " + d.ToLongDateString();
}
else
{
DailyDetailsPanel.Visible = false;
SelectedDate.Text = "No Events Scheduled For " + d.ToLongDateString();
}
}
privateDateTimeGetSafeDate(string proposedDate)
{
// Returns a non-null DateTime even if proposed date can't be parsed
DateTimesafeDate;
try
{
safeDate = DateTime.Parse(proposedDate, DateTimeFormatInfo.InvariantInfo);
}
catch (Exception e)
{
Response.Write("");
safeDate = DateTime.MinValue;
}
returnsafeDate;

}
public class MyCalendarEventData

{
private string m_ShortDesc;
private string m_DetailDesc;
privateDateTimem_EventDate;
private string m_StartTime;
private string m_EndTime;
public string ShortDesc
{
get {
returnm_ShortDesc;
}
set {
m_ShortDesc = value;
}
}
public string DetailDesc
{
get {
returnm_DetailDesc;
}
set {
m_DetailDesc = value;
}
}
publicDateTimeEventDate
{
get {
returnm_EventDate;
}
set {
m_EventDate = value;
}
}
public string StartTime
{
get {
returnm_StartTime;
}
set {
m_StartTime = value;
}
}
public string EndTime
{
get {
returnm_EndTime;
}

set {
m_EndTime = value;
}
}
}
</script>
</head>
<body>
<h4 style="text-align:right"><ahref= "EditTemplate.aspx">Admin</a></h4>
<h1 style="text-align:center">SPSU Calendar</h1><br />
<form id="MyCalendarForm" method="post" runat="server">
<p style="text-align:center">
<asp:Calendar id="MyCalendar"
runat="server"
Width="100%"
Height="350px"
CellPadding="2"
CellSpacing="1"
BorderColor="Beige"
DayHeaderStyle-BorderWidth="2"
DayHeaderStyle-BorderColor="ButtonFace"
SelectedDate="2010-04-13"
FirstDayOfWeek="Monday"
DayNameFormat="Full"
ShowDayHeader="True"
DayStyle-ForeColor="Black"
OtherMonthDayStyle-ForeColor="Purple"
OtherMonthDayStyle-Font-Italic="true"
DayStyle-Font-Underline="false"
DayStyle-Height="25"
ShowGridLines="True"
ShowNextPrevMonth="True"
ShowTitle="True"
nextprevstyle-backcolor="#FFCD13"
nextprevstyle-forecolor="Black"
nextprevstyle-font-bold="True"
nextprevstyle-font-size="Large"
TitleFormat="MonthYear"
TitleStyle-BackColor="#FFCD13"
TitleStyle-ForeColor="Black"
TitleStyle-Font-Size="Large"
TitleStyle-Font-Bold="True"
dayheaderstyle-backcolor="#C0C0C0"
dayheaderstyle-forecolor="Black"
daystyle-horizontalalign="Left"
daystyle-verticalalign="Top"
daystyle-font-size="Small"
SelectedDayStyle-Font-Bold="True"

selecteddaystyle-horizontalalign="Left"
selecteddaystyle-verticalalign="Top"
selecteddaystyle-font-size="Small"
selecteddaystyle-forecolor="#bd13dc"
TodayDayStyle-HorizontalAlign="Left"
TodayDayStyle-VerticalAlign="Top"
todaydaystyle-backcolor="White"
OnDayRender="MyCalendar_DayRender"
OnSelectionChanged="MyCalendar_SelectionChanged">
</asp:Calendar>
</p>
<asp:label id="SelectedDate" runat="server" font-size="Large" />
</p>
<asp:panel id="DailyDetailsPanel" runat="server">

<asp:Repeater id="DailyEventDetailRepeater" runat="server">
<HeaderTemplate>
<table border="1" width="100%">
<table style="color:Black;border-collapse:collapse;">
<tr style="color:White;background-color:0c75be;font-weight:bold;">
<td><b>Event</b></td>
<td><b>Description</b></td>
<td><b>Start Time</b></td>
<td><b>End Time</b></td>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr style="background-color:White;">
<td><%# DataBinder.Eval(Container.DataItem, "ShortDesc") %></td>
<td><%# DataBinder.Eval(Container.DataItem, "DetailDesc") %></td>
<td><%# DataBinder.Eval(Container.DataItem, "StartTime") %></td>
<td><%# DataBinder.Eval(Container.DataItem, "EndTime") %></td>
</tr>
</ItemTemplate>
<AlternatingItemTemplate>
<tr style="background-color:#CACACA;">
<td><%# DataBinder.Eval(Container.DataItem, "ShortDesc") %></td>
<td><%# DataBinder.Eval(Container.DataItem, "DetailDesc") %></td>
<td><%# DataBinder.Eval(Container.DataItem, "StartTime") %></td>
<td><%# DataBinder.Eval(Container.DataItem, "EndTime") %></td>
</tr>
</AlternatingItemTemplate>
<FooterTemplate>
</table>
</p>
</FooterTemplate>
</asp:Repeater>
</asp:panel>

</form>
</body>
</html>
The following code has been used to manage the database via the web interface only.
The interface provides the admin with the privileges to ‘ADD’, ‘MODIFY’ or ‘DELETE’
events directly from the web interface.
CODE
<%@ Page Language="c#" %>

<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.IO" %>
<script language="c#" runat="server">
voidPage_Load(object Sender, EventArgs E)

{
if (!Page.IsPostBack)
{
EventData.DataSource = LoadMyCalendarData();
EventData.DataBind();
}
}
protectedDataSetLoadMyCalendarData()
{
stringsourceXML = Server.MapPath("MyCalendar.xml");
if (!File.Exists(sourceXML))
{
return null;
}
DataSetcachedDataSet = (DataSet)Session["MyCalendarData"];
if (!(cachedDataSet == null))
{
returncachedDataSet;
}
DataSetdataSet = new DataSet();
try
{
dataSet.ReadXml(sourceXML);
Session["MyCalendarData"] = dataSet;
}
catch (Exception e)
{
ErrorMessage.Text = e.Message;
dataSet = null;
}
returndataSet;

}
voidDEDR_Edit(object Sender, DataGridCommandEventArgs E)

{
EventData.EditItemIndex = Convert.ToInt32(E.Item.ItemIndex);
}
voidDEDR_Update(object Sender, DataGridCommandEventArgs E)
{
int row = Convert.ToInt32(E.Item.ItemIndex);
TextBoxEditText=null;
EditText = (TextBox)E.Item.FindControl("txtEventDate");
dataSet.Tables[0].Rows[row]["EventDate"] = EditText.Text;
EditText = (TextBox)E.Item.FindControl("txtShortDesc");
dataSet.Tables[0].Rows[row]["ShortDesc"] = EditText.Text;
EditText = (TextBox)E.Item.FindControl("txtDetailDesc");
dataSet.Tables[0].Rows[row]["DetaiLDesc"] = EditText.Text;
EditText = (TextBox)E.Item.FindControl("txtStartTime");
dataSet.Tables[0].Rows[row]["StartTime"] = EditText.Text;
EditText = (TextBox)E.Item.FindControl("txtEndTime");
dataSet.Tables[0].Rows[row]["EndTime"] = EditText.Text;
dataSet.WriteXml(Server.MapPath("MyCalendar.xml"));
Session["MyCalendarData"] = null;
EventData.EditItemIndex = -1;
}
voidDEDR_Cancel(object Sender, DataGridCommandEventArgs E)

{
}
voidDEDR_Delete(object Sender, DataGridCommandEventArgs E)

{
int row = Convert.ToInt32(E.Item.ItemIndex);
dataSet.Tables[0].Rows[row].Delete();
}
voidDEDR_Add(object Sender, EventArgs E)

{
DataRownewRow;
newRow = dataSet.Tables[0].NewRow();
newRow["EventDate"] = "";
newRow["ShortDesc"] = "";
newRow["DetailDesc"] = "";
newRow["StartTime"] = "";
newRow["EndTime"] = "";
dataSet.Tables[0].Rows.Add(newRow);
EventData.EditItemIndex = (EventData.Items.Count - 1);
}
</script>
<html>
<head></head>
<body>
<h4 style="text-align:right;"><ahref="Default.aspx">Calendar</a></h4>
<formrunat="server">
<asp:Label id="ErrorMessage" runat="server" /><br/>
<asp:LinkButtonOnClick="DEDR_Add" Text="Add new event"

runat="server"/><br/>
<asp:DataGrid id="EventData"
AutoGenerateColumns="false" width="100%"
runat="server"
OnEditCommand="DEDR_Edit"
OnUpdateCommand="DEDR_Update"
OnCancelCommand="DEDR_Cancel"
OnDeleteCommand="DEDR_Delete">
<HeaderStyleForeColor="White” BackColor="DodgerBlue" Font-Bold="true"/>
<ItemStyleBackColor="White"/>
<AlternatingItemStyleBackColor="Gainsboro"/>
<Columns>
<asp:TemplateColumnHeaderText="Event Date">
<ItemTemplate>
<%# DataBinder.Eval(Container.DataItem, "EventDate") %>
</ItemTemplate>
<EditItemTemplate>

<asp:TextBox id="txtEventDate" Size="25"
Text='<%# DataBinder.Eval(Container.DataItem, "EventDate") %>'
runat="server"/>
</EditItemTemplate>
</asp:TemplateColumn>
<asp:TemplateColumnHeaderText="Event">
<ItemTemplate>
<%# DataBinder.Eval(Container.DataItem, "ShortDesc")%>
</ItemTemplate>
<EditItemTemplate>
<asp:TextBox id="txtShortDesc" MaxLength="25"
Text='<%# DataBinder.Eval(Container.DataItem, "ShortDesc") %>'
runat="server"/>
</EditItemTemplate>
<asp:TemplateColumnHeaderText="Description">
<ItemTemplate>
<%# DataBinder.Eval(Container.DataItem, "DetailDesc")%>
</ItemTemplate>
<EditItemTemplate>
<asp:TextBox id="txtDetailDesc" MaxLength="50"
Text='<%# DataBinder.Eval(Container.DataItem, "DetailDesc") %>'
runat="server"/>
</EditItemTemplate>
<asp:TemplateColumnHeaderText="Start Time">
<ItemTemplate>
<%# DataBinder.Eval(Container.DataItem, "StartTime")%>
</ItemTemplate>
<EditItemTemplate>
<asp:TextBox id="txtStartTime" MaxLength="7"
Text='<%# DataBinder.Eval(Container.DataItem, "StartTime") %>'
runat="server"/>
</EditItemTemplate>
<asp:TemplateColumnHeaderText="EndTime">
<ItemTemplate>
<%# DataBinder.Eval(Container.DataItem, "EndTime")%>
</ItemTemplate>
<EditItemTemplate>
<asp:TextBox id="txtEndTime" MaxLength="7"
Text='<%# DataBinder.Eval(Container.DataItem, "EndTime") %>'
runat="server"/>
</EditItemTemplate>
<asp:TemplateColumn>

<ItemTemplate>
<asp:LinkButtonCommandName="Edit"
Text="Edit" runat="server"/>
<asp:LinkButtonCommandName="Delete"
Text="Delete" runat="server"/>
</ItemTemplate>
<EditItemTemplate>
<asp:LinkButtonCommandName="Cancel"
Text="Cancel" runat="server"/>
<asp:LinkButtonCommandName="Update"
Text="Update" runat="server"/>
</EditItemTemplate>
</Columns>
</asp:DataGrid>
</form>
</body>
</html>

Database file:
<?xml version="1.0" standalone="yes"?>
<MyCalendar>
<Event>
<ShortDesc>Last Date for deposition of fee</ShortDesc>
<DetailDesc>This is the last date for deposition of fee. After this date the
students will be charged a fine of 100 rs per day.</DetailDesc>
<EventDate>2010/01/06</EventDate>
<StartTime>12:00AM</StartTime>
<EndTime>11:59PM</EndTime>
</Event>
<Event>
<ShortDesc>Extra-Curricular Activities</ShortDesc>
<DetailDesc>There will beextra-curricular activities in which various games will
be played like football,cricket,volleyball,etc.and there will various types of
cultural festivals will be organised and it will be for a week.</DetailDesc>
</Event>
<Event>
<ShortDesc>Republic Day</ShortDesc>
<DetailDesc>There will be republic day celebration on this day and flag hosting
will be done by our President Mr Ashok Ghosh.</DetailDesc>
</Event>
<Event>
<ShortDesc>Assignment-1</ShortDesc>
<DetailDesc>This is the date for issuing of all the assignments.</DetailDesc>
</Event>
</MyCalendar>
8.1 Objective of Testing:

Testing meets 3 objectives:
1. Identification of Errors:
These are obvious anomalies that show up in the behavior of a program or a unit or a
component. Such behavior as the following is considered an error
• Inserting same id in database
• Fetching from database
• Update in database
• Actions that do not execute as promised: The update menu does not update properly etc.
2. Conformance to requirements:
These errors are the result of testing the functions in the software against the
Requirements Definition Document to ensure that every requirement, functional or non-
functional is in the system and that it operates properly. This is often called
an Operational Qualification (OQ). However, note that even if some of the
requirements do not seem to be “Operational”, this is an operational test. For example, the
software may be required to display copyright messages on all acquired components. If
the messages are not displayed, then there is a lack of conformance and the system does
not operate properly.
3. Performance Qualification:
These are not “errors” as such but failures to conform to performance requirements.
Technically, they can be part of the second type. However,
PerformanceQualification (PQ) became a standard way of testing for historical reasons.
8.2 Types of Software Testing

Unit
testing
Module
testing
Sub-system
testing
System
testing
Acceptance
testing
Component Integration testing User

testing testing
Software testing is an investigation conducted to provide stakeholders with information about the
quality of the product or service under test.Software testing also provides an objective, independent
view of the software to allow the business to appreciate and understand the risks of software
implementation. Test techniques include, but are not limited to, the process of executing a program or
application with the intent of finding software bugs.
 Unit testing
Individual components are tested
 Module testing
Related collections of dependent components are tested
 Sub-system testing
Modules are integrated into sub-systems and tested. The focus here should be on interface
testing
 System testing
Testing of the system as a whole. Testing of emergent properties
 Acceptance testing
Testing with customer data to check that it is acceptable
8.3 Software Testing Life Cycle

Every organization has to undertakes testing of each of its products. However, the way it is conducted
differs from one organization to another. This refers to the life cycle of the testing process. It is
advisable to carry out the testing process from the initial phases, with regard to the Software
Development Life Cycle or SDLC to avoid any complications.
8.4 Software Testing Life Cycle Phases

Software testing has its own life cycle that meets every stage of the SDLC. The software testing life
cycle diagram can help one visualize the various software testing life cycle phases. They are
1. Requirement Stage
2. Test Planning
3. Test Analysis
4. Test Design

5. Test Verification and Construction
6. Test Execution
7. Result Analysis
8. Bug Tracking
9. Reporting and Rework
10. Final Testing and Implementation
11. Post Implementation
Requirement Stage
It is the initial stage of the life cycle process in which the developers take part in analysing the
requirements for designing a product. Testers can also involve themselves as they can think from the
users' point of view which the developers may not. Thus a panel of developers, testers and users can
be formed.
TestPlanning
Test planning is predetermining a plan well in advance to reduce further risks. Without a good plan,
no work can lead to success be it software-related or routine work. A test plan document plays an

important role in achieving a process-oriented approach. Once the requirements of the project are
confirmed, a test plan is documented. The test plan structure is as follows:
1. Introduction: This describes the objective of the test plan.

2. Test Items The items that are referred to prepare this document will be listed here such as
SRS, project plan.
3. Features to be tested: This describes the coverage area of the test plan, ie. the list of features
that are to be tested that are based on the implicit and explicit requirements from the
customer.
4. Features not to be tested: The incorporated or comprised features that can be skipped from the
testing phase are listed here. Features that are out of scope of testing, like incomplete modules
or those on low severity eg. GUI features that don't hamper the further process can be
included in the list.
5. Approach: This is the test strategy that should be appropriate to the level of the plan. It should
be in acceptance with the higher and lower levels of the plan.
6. Item pass/fail criteria: Related to the show stopper issue. The criterion which is used has to
explain which test item has passed or failed.
7. Suspension criteria and resumption requirements: The suspension criterion specifies the
criterion that is to be used to suspend all or a portion of the testing activities, whereas
resumption criterion specifies when testing can resume with the suspended portion.
8. Test deliverable: This includes a list of documents, reports, charts that are required to be
presented to the stakeholders on a regular basis during testing and when testing is completed.
9. Testing tasks: This stage is needed to avoid confusion whether the defects should be reported
for future function. This also helps users and testers to avoid incomplete functions and
prevent waste of resources.
10.Environmental needs: The special requirements of that test plan depending on the
environment in which that application has to be designed are listed here.
11.Responsibilities: This phase assigns responsibilities to the person who can be held responsible
in case of a risk.
12.Staffing and training needs: Training on the application/system and training on the testing
tools to be used needs to be given to the staff members who are responsible for the
application.
13.Risks and contingencies: This emphasizes on the probable risks and various events that can
occur and what can be done in such situation.
14.Approval: This decides who can approve the process as complete and allow the project to
proceed to the next level that depends on the level of the plan.
Test Analysis
once the test plan documentation is done, the next stage is to analyse what types of software testing
should be carried out at the various stages of SDLC.
Test Design
Test design is done based on the requirements of the project documented in the SRS. This phase
decides whether manual or automated testing is to be done. In automation testing, different paths for
testing are to be identified first and writing of scripts has to be done if required. There originates a
need for an end to end checklist that covers all the features of the project.

Test Verification and Construction
In this phase test plans, the test design and automated script tests are completed. Stress and
performance testing plans are also completed at this stage. When the development team is done with a
unit of code, the testing team is required to help them in testing that unit and reporting of the bug if
found. Integration testing and bug reporting is done in this phase of the software testing life cycle.
Test Execution
Planning and execution of various test cases is done in this phase. Once the unit testing is completed,
the functionality of the tests is done in this phase. At first, top level testing is done to find out top
level failures and bugs are reported immediately to the development team to get the required
workaround. Test reports have to be documented properly and the bugs have to be reported to the
development team.
Result Analysis
Once the bug is fixed by the development team, i.e after the successful execution of the test case, the
testing team has to retest it to compare the expected values with the actual values, and declare the
result as pass/fail.
Final Testing and Implementation

This phase focuses on the remaining levels of testing, such as acceptance, load, stress, performance
and recovery testing. The application needs to be verified under specified conditions with respect to
the SRS. Various documents are updated and different matrices for testing are completed at this stage
of the software testing life cycle.
Post Implementation
Once the tests are evaluated, the recording of errors that occurred during various levels of the software
testing life cycle, is done. Creating plans for improvement and enhancement is an ongoing process.
This helps to prevent similar problems from occuring in the future projects. In short, planning for
improvement of the testing process for future applications is done in this phase.
8.4Testing Phases:
Requirements System System Detailed

specification specification design design
System Sub-system Module and

Acceptance
integration integration unit code
test plan
test plan test plan and tess
Acceptance System Sub-system

Service
test integration test integration test

8.5 Test Cases
Test Cases
Module Name: Event Calendar
Test Case ID: REG1 Test Case Description:-Verifying possible outputs of registration form
applying all possible combination of inputs and simultaneously and checking current status.
CONCLUSIONS & REMARKS:
The web form event calendar has been prepared with great excitement and enthusiasm. It required a
lot of efforts and hard work, which was possible only by team work. The characteristics of this
software which make it more effective and efficient from existing system are as follows:
(a) It provides a better GUI environment to user.
(b) It provides an efficient security system to the software.
(c) The database is flexible.
(d) All work is computerized, so, no man power is required.
(e) The application provides platform independent software.
(f) It is easily understandable and reliable.
(g) The users requirement is fulfilled.
BIBLIOGRAPHY

A few textbooks were consulted before starting work on the project, and some of them were found to
be quite useful. Apart from textbooks, information from internet was also gathered.
REFERNCES: TEACH YOUR SELF ASP. NET IN 24 HOURS.
Websites: 1. www.google.com

Experiment 1: 1. The Web Form-My Calendar Introduction

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Experiment 1: 1. The Web Form-My Calendar Introduction

Transféré par

Droits d'auteur :

Formats disponibles

Experiment 1

1. THE WEB FORM-MY CALENDAR INTRODUCTION

The tasks performed during this phase were as follows:

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

4. SYSTEM DEVELOPMENT METHODOLOGY

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC),or Software Development Life Cycle in

The Development Life-Cycle

• A project is a set of activities, interactions and results.

• Development model definition (personal): A particular interaction configuration of development

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

• Implementation: The real code is written here.

An SDLC has three primary business objectives:

• Ensure the delivery of high quality systems;

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Provide Strong Management Control

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Process: Process Model for the Project.

The waterfall model

• Separate and distinct phases of specification and development

The stages of "The Waterfall Model" are:

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

• Whether the required technology is available or not

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

A Software Requirements Specification (SRS) - a requirements specification for a software system - is a

Software Requirements Specification

“THE WEB FORM-MY CALENDAR”

November 21, 2010

Version Changes Made Date

1.0 Not Applicable 28/05/2010

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Abbreviations are not used here.

2. The Overall Description

2.1 Product Perspective

2.2 Product Function

2.3 User Characteristics

2.5 User Interfaces

2.6 Assumptions and Dependencies.

3.1 Software Interfaces

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Use Case Diagram:

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

<%@ Page Language="c#" %>

public void MyCalendar_SelectionChanged(object sender, EventArgs e)

protected void page_load(object sender, EventArgs e)

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

protected void MyCalendar_DayRender(object sender, DayRenderEventArgs e)

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

ArrayListaEvents = new ArrayList();

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

public class MyCalendarEventData

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha

<asp:panel id="DailyDetailsPanel" runat="server">

Asoj Talesra, BhawinKabra, Kapil Raj Dhaybhai, Mahendra S Rajput, GauravOjha