You are on page 1of 36

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

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

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)

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

Kapil Raj Dhaybhai. with higher quality. In other words. • Provide strong management controls. in less time. • Maximize productivity. A number of system development life cycle (SDLC) models have been created: waterfall. fountain. and synchronize and stabilize. design. including the following: • Project planning. is the waterfall model: a sequence of stages in which the output of each stage becomes the input for the next. analysis. process diagrams. rapid prototyping. • Acceptance. then checks for errors. additions. such as planning. and the best known. Asoj Talesra. GauravOjha . the SDLC should ensure that we can produce more function. incremental. feasibility study: Establishes a high-level view of the intended project and determines its goals. goes on seemingly forever. Analyses end-user information needs. • Implementation: The real code is written here. BhawinKabra. pseudo code and other documentation. These stages can be characterized and divided up in different ways. and implementation. Mahendra S Rajput. business rules. deployment: The final stage of initial development. where the software is put into production and runs actual business. • Systems analysis. and are explained in the section below. • Integration and testing: Brings all the pieces together into a special testing environment. installation. An SDLC has three primary business objectives: • Ensure the delivery of high quality systems. including screen layouts. with fewer resources and in a predictable manner. the least glamorous and perhaps most important step of all. The oldest of these. bugs and interoperability. This. • 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. • Maintenance: What happens during the rest of the software's life: changes. and moves to a different computing platform and more. requirements definition: Refines project goals into defined functions and operation of the intended application. correction. • Systems design: Describes desired features and operations in detail. and spiral build and fix.

tactical and operational planning. is it functionally robust. The business could have taken the money spent on developingand running the system and spent it on advertising. The SDLC must ensure thatmanagement has timely. BhawinKabra.Ensure High Quality Before we can ensure that a system has high quality. and/or improved decision support for strategic. complete and accurate information on the status of the projectand the system throughout the development process. time and money on the project. how long a project will take. how many resources it willrequire and how much it will cost. as early as possible. staff raises ormany other things. Provide Strong Management Control The essence of strong management controls is predictability and feedback.The primary definition of quality in a business context is the return on investment (ROI)achieved by the system. The SDLC must ensure that such planning estimates can be put together before there have been any significant expenditures of resources. Projects maylast for many months or even years. This ROI can be operational cost savings or cost avoidance. The feedback process tells us how well weare doing in meeting the plan and the project's objectives. Mahendra S Rajput. improved product flexibility resulting in a larger market share. Predictability is provided by being able to accuratelyestimate. we must know what quality is in a business context. etc. product development. This definition of quality centres on the characteristics of the system itself: is it zero defect. ability to provide the best possible ROI. GauravOjha . is it well-structured. Asoj Talesra. Kapil Raj Dhaybhai. it is well-documented.

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

BhawinKabra. Kapil Raj Dhaybhai. 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.Experiment 3 Process: Process Model for the Project. The stages of "The Waterfall Model" are: Asoj Talesra. GauravOjha . Mahendra S Rajput. the waterfall model suited the best with minimum expenditure on both time and cost.

so the issues related to the system are solved after deployment of the system. The requirements are gathered from the end-user by consultation. this is referred to as Unit Testing. Unit testing mainly verifies if the modules/units meet their specifications. problems with the system developed (which are not found during the development life cycle) come up after its practical use starts. The system is first developed in small programs called units. Generally. Finally. Operations & Maintenance: This phase of "The Waterfall Model" is virtually never ending phase (Very long). After successfully testing the software. Asoj Talesra. 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. The system design specifications serve as input for the next phase of the model. which are integrated in the next phase. GauravOjha . the system is first divided in units which are developed and tested for their functionalities. Kapil Raj Dhaybhai. a Requirement Specification document is created which serves the purpose of guideline for the next phase of the model. hence this process is referred as Maintenance. Integration & System Testing: As specified above. it is delivered to the customer. Implementation & Unit Testing: On receiving system design documents. these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied. Mahendra S Rajput. Not all the problems come in picture directly but they arise time to time and needs to be solved. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. System & Software Design: Before a starting for actual coding. 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. Each unit is developed and tested for its functionality.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 work is divided in modules/units and actual coding is started. BhawinKabra.

GauravOjha . Asoj Talesra. Operation must be cost efficient as well as easily maintainable. Generally. violations. As the name suggests. Behavioural Feasibility The system must be able to handle multiple users simultaneously filling the registration the form. • Whether the required technology is available or not • Whether the required resources are available • Manpower. The operation of project must not incur any extra resources causing an overhead. In case of erroneous input the system must display the problem at the client side. the most important is cost-benefit analysis. Economic analysis is used for evaluating the effectiveness of the proposed system. the system can be judged to be economically feasible. Mahendra S Rajput. a feasibility study precedes technical development and project implementation. cost benefit analysis is done in which expected costs and benefits are evaluated. For evaluating this. a feasibility study is an evaluation or analysis of the potential impact of a proposed project. it is an analysis of the costs to be incurred in the system and benefits derivable out of the system.Experiment 4 Project Plan A feasibility study is an evaluation of a proposal designed to determine the difficulty in carrying out a designated task. In economic feasibility. Economic Feasibility For any system if the expected benefits equal or exceed the expected costs. Technical Feasibility In technical feasibility the following issues are taken into consideration. Since it might happen that developing a particular system may be technically possible but it may require huge investments and benefits may be less. In other words. In economic feasibility. it is important to consider the monetary factors also. liability. and legal other traps frequently unknown to the technical staff. The above factors have been well considered and the project is feasible from operation point of view. 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. BhawinKabra. testers & debuggers • Software and hardware Once the technical feasibility is established. Operational Feasibility Operational feasibility is mainly concerned with issues like whether the system will be used if it is developed and implemented. It includes study concerning contracts. Kapil Raj Dhaybhai. 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.programmers. economic feasibility of the proposed system is carried out.

Mahendra S Rajput. effort. 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? Asoj Talesra.• 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. Kapil Raj Dhaybhai. skills. GauravOjha . BhawinKabra. 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.

Use cases are also known as functional requirements. quality standards. Kapil Raj Dhaybhai. Software Requirements Specification For “THE WEB FORM-MY CALENDAR” By: Sparsh Gupta-07CS000061 & Yadunandan Shrimali-07CS000071 November 21. It includes a set of use cases that describe all the interactions the users will have with the software. the SRS also contains non-functional (or supplementary) requirements. In addition to use cases. GauravOjha . BhawinKabra.a requirements specification for a software system . Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements. Mahendra S Rajput. 2010 Version Changes Made Date 1.Experiment 5 SOFTWARE REQUIREMENTS SPECIFICATION A Software Requirements Specification (SRS) .0 Not Applicable 28/05/2010 Asoj Talesra. or design constraints).is a complete description of the behaviour of a system to be developed.

2.1 Product Perspective This product is a event calendar and will be developed on Asp. 1.The system must be good looking and must be easily updatable.5 User Interfaces The Login page should work and be tested against • Internet Explorer 8 • Firefox 3 2. 3. GauravOjha .1. Kapil Raj Dhaybhai. 2. SPECIFIC REQUIREMENTS 3.6 Assumptions and Dependencies. There are no development assumptions or dependencies.Net .1 Software Interfaces There are no special software interface requirements.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.3 Abbreviations Abbreviations are not used here.4 Constraints The form has to be developed on windows platform. Introduction. Asoj Talesra.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. BhawinKabra. 1. Mahendra S Rajput.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. 2. 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 . 1. 2. The Overall Description 2.

The primary elements are termed as “actors” and the processes are called “use cases” . GauravOjha . Asoj Talesra. BhawinKabra. This section describes in detail description of those diagrams. Mahendra S Rajput. Kapil Raj Dhaybhai.The use case diagram shows which actors interact with each use case. 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.

Asoj Talesra.ENTITY RELATIONSHIP DIAGRAM: It represents the object-relationship pairs in graphical forms. we can say that the primary goal of E-R diagrams is to represent data objects along with their relationships. Mahendra S Rajput. Thus. GauravOjha . Attributes which specify various properties of entities and relations involved in a system. 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. BhawinKabra. Kapil Raj Dhaybhai.

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

Mahendra S Rajput. GauravOjha . Kapil Raj Dhaybhai.Experiment 7 PROJECT DESIGN Database View Asoj Talesra. BhawinKabra.

BhawinKabra. Mahendra S Rajput.Database View while updating Asoj Talesra. Kapil Raj Dhaybhai. GauravOjha .

} DataSetcachedDataSet = (DataSet)Session["MyCalendarData"].ReadXml(sourceXml). } } protectedDataSetLoadMyCalendarData() { //This function is to load calendar data by connecting to database. if (!(File. } DataSetdataSet = new DataSet().IO" %> <%@ Import Namespace="System. } protected void page_load(object sender. Session["MyCalendarData"] = dataSet.Globalization" %> <html> <head><title>Event Calendar</title> <script language="c#" runat="server"> public void MyCalendar_SelectionChanged(object sender. try { dataSet.Text = e. EventArgs e) { //This function will be called on selection of any date.MapPath("MyCalendar.Data"%> <%@ Import Namespace="System. Mahendra S Rajput.Message. Asoj Talesra. GauravOjha . BhawinKabra. Kapil Raj Dhaybhai. if (cachedDataSet != null) { returncachedDataSet. } catch (Exception e) { SelectedDate. ShowDailyEvents(). stringsourceXml = Server.IsPostBack)) { ShowDailyEvents(). EventArgs e) { if (!(Page.xml").Experiment 8 PROJECT CODING <%@ Page Language="c#" %> <%@ Import Namespace="System.Exists(sourceXml))) { return null.

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

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

GauravOjha .} public class MyCalendarEventData { private string m_ShortDesc. } } public string StartTime { get { returnm_StartTime. } } publicDateTimeEventDate { get { returnm_EventDate. } Asoj Talesra. BhawinKabra. } set { m_EventDate = value. Mahendra S Rajput. private string m_DetailDesc. privateDateTimem_EventDate. } } public string DetailDesc { get { returnm_DetailDesc. private string m_EndTime. } set { m_DetailDesc = value. } } public string EndTime { get { returnm_EndTime. Kapil Raj Dhaybhai. } set { m_ShortDesc = value. public string ShortDesc { get { returnm_ShortDesc. } set { m_StartTime = value. private string m_StartTime.

} } } </script> </head> <body> <h4 style="text-align:right"><ahref= "EditTemplate.set { m_EndTime = value. BhawinKabra. GauravOjha . Mahendra S Rajput.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" Asoj Talesra. Kapil Raj Dhaybhai.

Kapil Raj Dhaybhai."> <td><%# DataBinder. "DetailDesc") %></td> <td><%# DataBinder.Eval(Container. "StartTime") %></td> <td><%# DataBinder.Eval(Container. GauravOjha .background-color:0c75be.DataItem.Eval(Container. "ShortDesc") %></td> <td><%# DataBinder.Eval(Container.DataItem.Eval(Container.DataItem. "EndTime") %></td> </tr> </ItemTemplate> <AlternatingItemTemplate> <tr style="background-color:#CACACA. "EndTime") %></td> </tr> </AlternatingItemTemplate> <FooterTemplate> </table> </p> </FooterTemplate> </asp:Repeater> </asp:panel> Asoj Talesra.DataItem. "ShortDesc") %></td> <td><%# DataBinder.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> <p style="text-align:center"> <asp:label id="SelectedDate" runat="server" font-size="Large" /> </p> <asp:panel id="DailyDetailsPanel" runat="server"> <asp:Repeater id="DailyEventDetailRepeater" runat="server"> <HeaderTemplate> <p style="text-align:center"> <table border="1" width="100%"> <table style="color:Black.DataItem."> <td><%# DataBinder. BhawinKabra.Eval(Container.DataItem."> <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."> <tr style="color:White.Eval(Container.font-weight:bold.border-collapse:collapse.DataItem. Mahendra S Rajput. "StartTime") %></td> <td><%# DataBinder.DataItem. "DetailDesc") %></td> <td><%# DataBinder.Eval(Container.

dataSet = null.Text = e.Exists(sourceXML)) { return null. Asoj Talesra. } returndataSet. BhawinKabra. } DataSetdataSet = new DataSet(). try { dataSet.IO" %> <script language="c#" runat="server"> voidPage_Load(object Sender. } } protectedDataSetLoadMyCalendarData() { stringsourceXML = Server.DataSource = LoadMyCalendarData(). Kapil Raj Dhaybhai.ReadXml(sourceXML). if (!File.DataBind().</form> </body> </html> The following code has been used to manage the database via the web interface only. } catch (Exception e) { ErrorMessage.MapPath("MyCalendar. The interface provides the admin with the privileges to ‘ADD’.Data" %> <%@ Import Namespace="System. GauravOjha . Mahendra S Rajput. if (!(cachedDataSet == null)) { returncachedDataSet. ‘MODIFY’ or ‘DELETE’ events directly from the web interface. CODE <%@ Page Language="c#" %> <%@ Import Namespace="System.Message. Session["MyCalendarData"] = dataSet. } DataSetcachedDataSet = (DataSet)Session["MyCalendarData"]. EventData.IsPostBack) { EventData.xml"). EventArgs E) { if (!Page.

Tables[0].DataBind().DataSource = LoadMyCalendarData(). DataGridCommandEventArgs E) { DataSetdataSet = LoadMyCalendarData(). EventData. Mahendra S Rajput.DataBind().ToInt32(E.Rows[row]["StartTime"] = EditText.Rows[row].Tables[0]. dataSet.ItemIndex).Tables[0].MapPath("MyCalendar.ItemIndex). EventData. EventData.Item.WriteXml(Server.Tables[0].Item. DataGridCommandEventArgs E) { EventData.Text. } voidDEDR_Cancel(object Sender. Kapil Raj Dhaybhai. } voidDEDR_Delete(object Sender. dataSet. EditText = (TextBox)E. dataSet. Session["MyCalendarData"] = null.Item.FindControl("txtShortDesc"). EventData. EventData.Tables[0].xml")).DataSource = LoadMyCalendarData(). Session["MyCalendarData"] = null. EditText = (TextBox)E.Text. TextBoxEditText=null. dataSet.FindControl("txtStartTime").Rows[row]["ShortDesc"] = EditText.} voidDEDR_Edit(object Sender. dataSet. DataGridCommandEventArgs E) { EventData. dataSet. EventData. EventData.Item. int row = Convert. EventData.Rows[row]["DetaiLDesc"] = EditText.EditItemIndex = -1. } voidDEDR_Update(object Sender.FindControl("txtEventDate").ToInt32(E. DataGridCommandEventArgs E) { DataSetdataSet = LoadMyCalendarData().Text. GauravOjha .Delete(). EventArgs E) Asoj Talesra. dataSet.EditItemIndex = -1.EditItemIndex = Convert.Item. Session["MyCalendarData"] = null.ItemIndex).DataSource = LoadMyCalendarData().Text. int row = Convert. dataSet.DataBind().Rows[row]["EndTime"] = EditText.Item.Item.DataBind(). EditText = (TextBox)E.FindControl("txtDetailDesc"). } voidDEDR_Add(object Sender. EventData.xml")).MapPath("MyCalendar.FindControl("txtEndTime").WriteXml(Server. EventData.ToInt32(E. EditText = (TextBox)E.EditItemIndex = -1.Text.Item.Tables[0]. BhawinKabra.DataSource = LoadMyCalendarData().Rows[row]["EventDate"] = EditText. EditText = (TextBox)E.

EventData. EventData. newRow = dataSet. Session["MyCalendarData"] = null.{ DataSetdataSet = LoadMyCalendarData().Count . GauravOjha . newRow["EndTime"] = "". EventData.Rows. EventData. newRow["ShortDesc"] = "". newRow["DetailDesc"] = "".DataSource = LoadMyCalendarData().WriteXml(Server.Items. dataSet. EventData. Mahendra S Rajput. newRow["EventDate"] = "". dataSet.NewRow()."><ahref="Default. } </script> <html> <head></head> <body> <h4 style="text-align:right.xml")).DataBind(). Kapil Raj Dhaybhai.MapPath("MyCalendar.Add(newRow). newRow["StartTime"] = "".Eval(Container.Tables[0]. "EventDate") %> </ItemTemplate> <EditItemTemplate> Asoj Talesra.DataItem.DataSource = LoadMyCalendarData().EditItemIndex = (EventData. DataRownewRow.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.Tables[0].1).DataBind(). BhawinKabra.

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

GauravOjha . Mahendra S Rajput. BhawinKabra.<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> </asp:TemplateColumn> </Columns> </asp:DataGrid> </form> </body> </html> Asoj Talesra. Kapil Raj Dhaybhai.

0" standalone="yes"?> <MyCalendar> <Event> <ShortDesc>Last Date for deposition of fee</ShortDesc> <DetailDesc>This is the last date for deposition of fee.</DetailDesc> <EventDate>2010/01/18</EventDate> <StartTime>12:00AM</StartTime> <EndTime>11:59PM</EndTime> </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. Mahendra S Rajput.</DetailDesc> <EventDate>2010/01/27</EventDate> <StartTime>12:00AM</StartTime> <EndTime>11:59PM</EndTime> </Event> </MyCalendar> 8.</DetailDesc> <EventDate>2010/01/26</EventDate> <StartTime>12:00AM</StartTime> <EndTime>11:59PM</EndTime> </Event> <Event> <ShortDesc>Assignment-1</ShortDesc> <DetailDesc>This is the date for issuing of all the assignments.cricket.Database file: <?xml version="1.etc.and there will various types of cultural festivals will be organised and it will be for a week.volleyball. After this date the students will be charged a fine of 100 rs per day. Kapil Raj Dhaybhai. GauravOjha . BhawinKabra.</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.1 Objective of Testing: Asoj Talesra.

This is often called an Operational Qualification (OQ). the software may be required to display copyright messages on all acquired components. 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. Kapil Raj Dhaybhai. For example. they can be part of the second type. functional or non- functional is in the system and that it operates properly. GauravOjha . note that even if some of the requirements do not seem to be “Operational”. then there is a lack of conformance and the system does not operate properly. 8.2 Types of Software Testing Asoj Talesra. 2. However. If the messages are not displayed. Technically. However. Mahendra S Rajput. this is an operational test. 3. BhawinKabra. Identification of Errors: These are obvious anomalies that show up in the behavior of a program or a unit or a component. PerformanceQualification (PQ) became a standard way of testing for historical reasons. Performance Qualification: These are not “errors” as such but failures to conform to performance requirements.Testing meets 3 objectives: 1. 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.

Testing of emergent properties  Acceptance testing Testing with customer data to check that it is acceptable 8. Mahendra S Rajput.4 Software Testing Life Cycle Phases Software testing has its own life cycle that meets every stage of the SDLC. The focus here should be on interface testing  System testing Testing of the system as a whole. Kapil Raj Dhaybhai.Software testing also provides an objective. This refers to the life cycle of the testing process. 8. They are 1. 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. the way it is conducted differs from one organization to another. Test Planning 3. but are not limited to. However. Test Design Asoj Talesra. It is advisable to carry out the testing process from the initial phases. Test techniques include. with regard to the Software Development Life Cycle or SDLC to avoid any complications.  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. Test Analysis 4. BhawinKabra. GauravOjha . Requirement Stage 2. the process of executing a program or application with the intent of finding software bugs.3 Software Testing Life Cycle Every organization has to undertakes testing of each of its products. The software testing life cycle diagram can help one visualize the various software testing life cycle phases. independent view of the software to allow the business to appreciate and understand the risks of software implementation.

Test Verification and Construction 6. Without a good plan. BhawinKabra. no work can lead to success be it software-related or routine work. Mahendra S Rajput. 5. Bug Tracking 9. Thus a panel of developers. 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. TestPlanning Test planning is predetermining a plan well in advance to reduce further risks. testers and users can be formed. Reporting and Rework 10. Result Analysis 8. Final Testing and Implementation 11. Testers can also involve themselves as they can think from the users' point of view which the developers may not. Kapil Raj Dhaybhai. GauravOjha . Test Execution 7. A test plan document plays an Asoj Talesra.

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

The application needs to be verified under specified conditions with respect to the SRS. Test reports have to be documented properly and the bugs have to be reported to the development team. is done. the test design and automated script tests are completed. Post Implementation Once the tests are evaluated. BhawinKabra. Kapil Raj Dhaybhai. Test Execution Planning and execution of various test cases is done in this phase. Result Analysis Once the bug is fixed by the development team. the recording of errors that occurred during various levels of the software testing life cycle. Integration testing and bug reporting is done in this phase of the software testing life cycle.e after the successful execution of the test case. stress. load. Creating plans for improvement and enhancement is an ongoing process. such as acceptance. the testing team has to retest it to compare the expected values with the actual values. 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. the functionality of the tests is done in this phase. planning for improvement of the testing process for future applications is done in this phase. Once the unit testing is completed. Final Testing and Implementation This phase focuses on the remaining levels of testing. At first. This helps to prevent similar problems from occuring in the future projects. and declare the result as pass/fail. performance and recovery testing. i. When the development team is done with a unit of code. Stress and performance testing plans are also completed at this stage. GauravOjha . Various documents are updated and different matrices for testing are completed at this stage of the software testing life cycle.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 Asoj Talesra. In short. 8. Mahendra S Rajput.Test Verification and Construction In this phase test plans. the testing team is required to help them in testing that unit and reporting of the bug if found.

(d) All work is computerized. 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. GauravOjha . (f) It is easily understandable and reliable. (g) The users requirement is fulfilled. It required a lot of efforts and hard work. CONCLUSIONS & REMARKS: The web form event calendar has been prepared with great excitement and enthusiasm. (e) The application provides platform independent software. BIBLIOGRAPHY Asoj Talesra. no man power is required. Kapil Raj Dhaybhai. BhawinKabra.8. Mahendra S Rajput. (b) It provides an efficient security system to the software. which was possible only by team work. so.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. (c) The database is flexible.

www. NET IN 24 HOURS. REFERNCES: TEACH YOUR SELF ASP. and some of them were found to be quite useful. information from internet was also gathered. Mahendra S Rajput. Apart from textbooks. GauravOjha .com Asoj Talesra.google. Kapil Raj Dhaybhai.A few textbooks were consulted before starting work on the project. Websites: 1. BhawinKabra.