SDLC Report

for

Call Tracker Application

Version 1.0 approved

Prepared by

Pruthvi P(11co69)

Sukruth Ananth(11co96)

National Institute of Technology Karnataka, Surathkal

17/4/2014

SDLC Report for Call Tracker Application

Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii Revision History ........................................................................................................................... iii 1. Introduction ..............................................................................................................................1
1.1 1.2 1.3 1.4 2.1 2.2 2.3 3.1 3.2 3.3 3.4 3.5 4.1 4.2 4.3 4.4 4.5 5.1 5.2 5.3 5.4 6.1 6.2 6.3 6.4 6.5 7.1 7.2 7.3 7.4 7.5 Application Description............................................................................................................... 1 Need for your Application ........................................................................................................... 2 Application Domain and Targeted Audience .............................................................................. 1 Product Scope .............................................................................................................................. 2 Introduction about the Software Process Model Followed .......................................................... 3 Suitability of the Software Process Model .................................................................................. 3 Adoption of the Software Process Model .................................................................................... 3 RE Techniques used .................................................................................................................... 4 Tool(s) Used and its Features ...................................................................................................... 5 Suitability of the Tool(s).............................................................................................................. 6 Adoption of the Tool(s) ............................................................................................................... 6 Outcome of this activity .............................................................................................................. 6 Modeling Language(s) Used ....................................................................................................... 8 Tool(s) and its Features ............................................................................................................... 9 Suitability of the Tool(s).............................................................................................................. 9 Adoption of the Tool(s) ............................................................................................................... 9 Outcome of this Activity ............................................................................................................. 9 Tool(s) and its features .............................................................................................................. 10 Suitability of the tool(s) ............................................................................................................. 11 Adoption of the Tools ................................................................................................................ 12 Outcome of this Activity ........................................................................................................... 12 Testing Method(s) Used ............................................................................................................ 14 Tool(s) and its Features ............................................................................................................. 14 Suitability of the Tool(s)............................................................................................................ 15 Adoption of the Tool(s) ............................................................................................................. 16 Outcome of this Activity ........................................................................................................... 16 Software Project Management Activities Followed .................................................................. 17 Tool(s) and its Features ............................................................................................................. 17 Suitability of the Tool(s)............................................................................................................ 17 Adoption of the Tool(s) ............................................................................................................. 17 Outcome of this Activity ........................................................................................................... 18

2. Software Process Model ..........................................................................................................3

3. Requirements Analysis ............................................................................................................4

4. Design ........................................................................................................................................8

5. Development ...........................................................................................................................10

6. Testing .....................................................................................................................................14

7. Software Project Management .............................................................................................17

Appendix A: SRS Documentation ..............................................................................................19 Appendix B: Development Tools ................................................................................................19 Appendix C: Test Cases / Test Reports......................................................................................19

SDLC Report for Call Tracker Application

Page iii

Revision History
Name Date Reason For Changes Version

SDLC Report for Call Tracker Application

Page 1

1. Introduction
1.1 Application Description
Call tracking software records information about incoming telephone calls, but not the conversation. Call tracking is a technology which enables the pay per call business model, allowing the tracking of phone calls to be associated with performance based advertising, and supplying additional analytic information about the phone calls. Call tracking is a method of performance review for advertising. It is based on the technological possibility of measuring the behavior of callers and is thus the equivalent in telephony to the conversion tracking used on the internet. Via different channels, both procedures offer the opportunity of clearly assigning a customer response to a specific advertising medium. An application of call tracking is to monitor the effectiveness of advertising campaigns by comparing tracking reports before and after.

1.2 Application Domain and Targeted Audience

1.2.1 Application Domain
Particularly for high-priced, advising-intensive products such as cars or insurance, there are often queries via telephone. The calls happen relatively far along the click chain and, in some cases, they even speed up the purchasing process. Telephone tracking plays an important role in assigning these calls and the profit generated by them to an advertising channel. In addition, the significance of the call can be mapped in the purchasing chain and its position can be determined. If one takes conversion chains, to use an example, that contain a call, it becomes evident that usually this call occurs immediately preceding the profit. At the same time, it can be determined whether the shopping basket content tends to be greater when a customer has called in previously, or if the conversion chain is shorter in cases of caller participation, as the purchasing security of the customer is increased. These and other analyses are possible by means of telephone tracking and lead to a new assessment of the telephone as a channel and thus the marketing measures in this area. In the area of Google AdWords search engine advertising, telephone tracking can assign calls to the keyword level. This information can be used for campaign management by, for example, increasing the cost per click bid for keywords with a high request rate. A bid management system can carry out these tasks automatically and with high statistical precision and optimize them according to individual cost-per-caller goals. In order to optimize cost-per-caller or ROI goals, the incorporation of a bid management system is necessary.

1.2.2

Targeted Audience

The tracker will be used by agents to log call drivers which will help the operations team to provide more pertinent and effective coaching. The agent and the administrator both are benefited by this and hence the perspective of the product proves to be very effective. With the help of telephone tracking, new insights into the performance of online marketing are opened up to marketing managers. Until now, telephone contact interrupted or ended the click chain so that essentially no correct cost-per-order could be calculated. This hurdle of media discontinuity has been overcome with telephone tracking. Furthermore, this tracking method

SDLC Report for Call Tracker Application

Page 2

resolves the problem of correct assignment of orders placed by telephone. Online traders benefit primarily from this new technology.

1.3 Need for your Application

What number has called. The geographical location of a caller, if available. The time distribution of incoming calls. Recording of the phone call. The number of calls received is one of the main factor as it helps the administrator to notice the calls attended by a particular agent or employee to see the progress .The number of calls received is also responsible for the strategical management of the future plans regarding the development of the software and the management of the employees. The time distribution of incoming calls also reveals the sincerity of the employee and that can be very useful for the development of the project and the changes need to be made in the future. The recording of the phone call and the time of their problem being resolved is also a key concern and will play important role . The information of the call tracked can be used to generate reports such as, amongst others: Caller names and addresses (if a database relating numbers to names and addresses is available) Postal code summary Missed calls Call summaries (e.g., hourly, daily) Details of repeat and unique callers Analysis of frequency of calls by city and area code, if available

1.4 Application Scope

The main scope of the project is to decide the healthy weather of the working committee without calling their customers based on their complaints. The product can also be used by the administrator to check the development of the work in terms of efficiency. The administrator can also check the work done by each agent . The agent or the employee intern can check the calls made by a particular customer and whether his case is resolved or not . The Development of the project can be enhanced based on the needs of the agent and the effort being done to reduce the effort. Furthermore, this tracking method resolves the problem of correct assignment of orders placed by telephone.

SDLC Report for Call Tracker Application

Page 3

2. Software Process Model

2.1 Introduction about the Software Process Model Followed
2.1.1 Waterfall Model :
The waterfall model. This takes the fundamental process activities of specification, development, validation and evolution and represents them as separate process phases such as requirements specification, software design, implementation, testing and so on.

2.2 Suitability of the Software Process Model

Our application is a very specific event based application .Hence the system requirements were very clear and clearly understood. The customers, service providers (call center employees in our case) and the administrators requirements from the software was very clear with no ambiguity. Hence Waterfall model was chosen. The advantages of the waterfall model are that documentation is produced at each phase and that it fits with other engineering process models, and hence if in the coming years if there is more requirements specification and if more functions is required, then using the documentation at different phase, we can migrate to some other model. But for the present situation, waterfall model is suitable.

2.3 Adoption of the Software Process Model

The Water fall model was implemented in the following way. 1. Requirements analysis and definition: The system's services, constraints and goals were established by consultation with system users i.e the call center employees, customers details, and administrators requirement .They are then defined in detail and served as system specification. 2. System and software design: The systems design process partitions the requirements to either hardware or software systems. Hence different interfaces were designed for the call center employees and administrators both with different user rights. The interfaces were designed according to the requirement specifications. 3. Implementation and unit testing: During this stage, the software design is realized as asset of programs or program units. Hence we implemented our project on Visual studio creating separate classes for each type of system users. 4. Integration and system testing: Once all the units were created, all were joined and compiled for final result and testing was done accordingly to remove errors and bugs. 5. Operation and maintenance: The system is installed and regularly used and checked for errors and bugs.

SDLC Report for Call Tracker Application

Page 4

3. Requirements Analysis
3.1 RE Techniques used
Call Tracker Layout Mockup Main Call Reason: Multiple Reasons? Call Reason 2: Call Reason 3: Call Reason 4: Call Reason 5: Resolved? Escalated? Transferred? Conferenced? No Caller/Dead Air? Sale? Credit? Customer Satisfaction: [Yes or No] [Yes or No] [Yes or No] [Yes or No] [Yes or No] [Tick Box & $ Amt. Field] [Tick Box & $ Amt. Field] [Tick Boxes 1 through 5] CRT Timer [Timer] (See Item C, below) (See Item D, below) (See Item E, below) (See Item F, below) (See Item G, below) (See Item H, below) (See Item I, below) (See Item J, below) (See Item K, below) Conditionalonly appear based on response to Multiple Reasons?, above. [Dropdown Menu] [Yes or No] (See Item A, below) (See Item B, below)

(See Item B, below)

A.

Main Call Reason: The main call reason section should have a three-tiered dropdown menu (see attached Excel file for the complete list of menu selections).

SDLC Report for Call Tracker Application

Page 5

1.

The first tier of the menu should contain the Call Category (e.g., Account Maintenance, Billing, Customer Service or Troubleshooting); the user should hover over the call category to see the applicable secondary menu The second tier of the menu should allow the user to hover over a Call Type (e.g., change rate plan/feature); the user should hover over the call type to see the applicable tertiary menu The third tier of the menu should allow the user to click on the Call Reason (e.g., add feature)

2.

3.

If there are multiple reasons as of why the customer called, the operations team want the same levels above to appear in the call tracker. B. Multiple Reasons?:User should tick a box for either Yes or No. If Yes, then four more rows should appear underneath. These rows will be called Call Reason 2, Call Reason 3, Call Reason 4 and Call Reason 5. These rows should work the same way that Main Call Reason works, as described in Item A, above. Resolved?:User should tick a box for either Yes or No. Escalated?: User should tick a box for either Yes or No. Transferred?: User should tick a box for either Yes or No. 1. If Yes is selected, agent must indicate where the call was transferred to in a text box (can always be displayed). Conferenced?: User should tick a box for either Yes or No. No Caller/Dead Air?: User should tick a box for either Yes or No. Sale?:If a call results in a sale, the user ticks box next to this line item; If the user ticks the box, they must enter a dollar amount; amount field should require two decimal places. Credit?:If a call results in a credit, the user ticks box next to this line item; If the user ticks the box, they must enter a dollar amount; amount field should require two decimal places. Customer Satisfaction: User ticks one of five boxes that appear in this row; Boxes should be labelled one through five. CRT Timer: Display timer that begins when call commences and stops when call ends to track duration of various call types.

C. D. E.

F. G. H.

I.

J.

K.

3.2 Tool(s) Used and its Features

The requirement analysis tool that would be used for our software is the Visual Studio Requirements Modeling Framework (RMF). It is an open-source framework for working on

SDLC Report for Call Tracker Application

Page 6

requirements on the ReqIF standard. RMF is also the only tool which provides a GUI for the ReqIF files in the form of an application called ProR. One of the major problems in requirements analysis is that there is no standard format used across various tools. The eclipse RMF tries to change this by making a standard, ReqIF. This is an XML based data structure for exchanging requirements. The ReqIF format does not have any attributes and instead is simply a container for six elements: SpecObject Represents an actual requirement. Attributes of SpecObject depends on the SpecType. SpecType Contains a list of attributes which are named entities of certain data types. A SpecObject of a certain type has a value for each of the SpecType attributes. DatatypeDefinition Is an instance of one atomic data type that is configured to be used. Specification SpecObjects can be grouped together in a tree structure called Specification which is used to reference different SpecObjects. SpecRelation It is a link between different SpecObjects. It contains a source and a target. A SpecRelation can have a SpecType and thus can also have attributes. It also has the following features that are of great use to us: Requirements Management Requirements Engineering Requirements Traceability Change Management Product Line Engineering

3.3 Suitability of the Tool(s)

Since the RMF , it integrates very easily with the Visual Studio development IDE which involves a lesser time to familiarize ourselves with the development environment. Also, most other requirement analysis tools are outdated and do not have a proper standard for storing the requirements. Visual Studio RMF introduces a standard and also provides a GUI for easy viewing and editing of the requirements.

3.4 Adoption of the Tool(s)

We would be using the ProR GUI for RMF to provide us an easy way to manage all the requirements that are stored in the ReqIF standard format. These ReqIF files will contain information regarding all the requirements and the tool has a great feature of segregating different types of requirements. We can prioritize requirements and thus it helps us in managing the development of different components of the software.

3.5 Outcome of this activity

The use of such an application can help us in collecting, organizing, and analyzing the requirements in a very efficient manner. We can list down all the types of requirements and provide enough information for the development of the application. Here are some following screenshots of the RMF:

SDLC Report for Call Tracker Application

Page 7

SDLC Report for Call Tracker Application

Page 8

4. Design
4.1 Modeling Language(s) Used
4.1.1 Unified Modelling Language
UML is a general purpose modeling language. It was initially started to capture the behavior of complex software and non software system and now it has become an OMG standard. UML provides elements and components to support the requirement of complex systems. UML follows the object oriented concepts and methodology. So object oriented systems are generally modeled using the pictorial language. UML diagrams are drawn from different perspectives like design, implementation, deployment etc. UML Diagrams: Diagrams are the heart of UML. These diagrams are broadly categorized as structural and behavioral diagrams.

Structural diagrams are consists of static diagrams like class diagram, object diagram etc. Behavioral diagrams are consists of dynamic diagrams like sequence diagram, collaboration diagram etc.

The static and dynamic nature of a system is visualized by using these diagrams.

Structural UML diagrams Class diagram Component diagram Composite structure diagram Deployment diagram Object diagram Package diagram Profile diagram Behavioral UML diagrams Activity diagram Communication diagram Interaction overview diagram Sequence diagram State diagram Timing diagram Use case diagram

SDLC Report for Call Tracker Application

Page 9

4.2 Tool(s) and its Features

Argo UML : Argo UML is an UML diagramming application written in Java and released under the open source Eclipse Public License. By virtue of being a Java application. Features of the Argo UML tool:

Closely follows the UML standard. Platform independent Java 1.5+. Click and Go! with Java Web Start (no setup required, starts from your web browser).. Export diagrams as GIF, PNG, PS, EPS, PGML and SVG. Advanced diagram editing and zoom.

4.3 Suitability of the Tool(s)

The tool provides interface to standard UML diagrams which are required in our project SRS document, such as : Class diagram Use Case diagram Activity Diagram State diagram Component diagram etc.

4.4 Adoption of the Tool(s)

We have deployed all our UML diagrams using Argo UMl tool, which includes Class diagram Use Case diagram Activity Diagram State transition diagram Component diagram. Deployment diagram. Sequence diagram Collaboration diagram For deploying we have used the standard GUI provided by the tool and hence using the drag and drop technique we have connected various components and diagrams accordingly.

4.5 Outcome of this Activity

The outcome of this activity i.e the documents and diagrams are included in Appendix B.

SDLC Report for Call Tracker Application

Page 10

5. Development
5.1 Tool(s) and its features
5.1.1 Integrated Development Environment-Microsoft Visual Studio
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is used to develop computer programs for Microsoft Windows superfamily of operating systems, as well as web sites, web applications and web services. Visual Studio uses Microsoft software development platforms such as Windows API, Windows Forms, Windows Presentation Foundation, Windows Store and Microsoft Silverlight. It can produce both native code and managed code. Microsoft Visual Studio is the environment used in this project. Visual Studio includes a code editor supporting IntelliSense as well as code refactoring. The integrated debugger works both as a source-level debugger and a machine-level debugger. Other built-in tools include a forms designer for building GUIapplications, web designer, class designer, and database schema designer. It accepts plug-ins that enhance the functionality at almost every levelincluding adding support for source-control systems (like Subversion and Visual SourceSafe) and adding new toolsets like editors and visual designers for domain-specific languages or toolsets for other aspects of the software development lifecycle (like the Team Foundation Server client: Team Explorer). Visual Studio supports different programming languages and allows the code editor and debugger to support (to varying degrees) nearly any programming language, provided a language-specific service exists.Built-in languages include C,[5] C++and C++/CLI (via Visual C++) VB.NET (via Visual Basic .NET), C# (via Visual C#), and F# (as of Visual Studio 2010[6]). Support for other languages such as M, Python, and Ruby among others is available via language services installed separately. It also supports XML/XSLT, HTML/XHTML, JavaScript and CSS. Individual language-specific versions of Visual Studio also exist which provide more limited language services to the user: Microsoft Visual Basic, Visual J#, Visual C#, and Visual C++.

5.1.2 Application Development Frameworks, SDKs and APIs

A server-side web API is a programmatic interface to a defined request-response message system, typically expressed in JSON or XML, which is exposed via the webmost commonly by means of an HTTP-based web server. Mashups are web applications which combine the use of multiple such web APIs. Webhooks are server-side web APIs that take as input a URI that is designed to be used like a remote named pipe or a type of callback such that the server acts as a client to dereference the provided URI and trigger an event on another server which handles this event thus providing a type of peer-to-peer IPC.While "web API" in this context is sometimes considered a synonym for web service, Web 2.0 web applications have moved away from SOAP-based web services towards more cohesive collections of RESTful web resources. These RESTful web APIs are accessible via standard HTTP methods by a variety of HTTP clients including browsers and mobile devices.

5.1.3 Database Tools- Microsoft SQL Server

Microsoft SQL Server is a relational database management system developed by Microsoft. As a database, it is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another

SDLC Report for Call Tracker Application

Page 11

computer across a network (including the Internet). There are at least a dozen different editions of Microsoft SQL Server aimed at different audiences and for workloads ranging from small singlemachine applications to large Internet-facing applications with many concurrent users. Its primary query languages are T-SQL and ANSI SQL.

5.1.4 Web Servers- Internet Information Services(IIS)

Internet Information Services (IIS, formerly Internet Information Server) is an extensible web server created by Microsoft for use with Windows NT family.[2] IIS supports HTTP, HTTPS, FTP, FTPS, SMTP and NNTP. It has been an integral part of the Windows NT family since Windows NT 4.0, though it may be absent from some editions (e.g. Windows XP Home edition). IIS is not turned on by default when Windows is installed. The IIS Manager is accessed through the Microsoft Management Console or Administrative Tools in the Control Panel. IIS 6.0 and higher support the following authentication mechanisms:[13]

Anonymous authentication Basic access authentication Digest access authentication Integrated Windows Authentication

5.1.5 Build Tools

Apache Ant is a software tool for automating software build processes. It is similar to Make but is implemented using the Java language, requires the Java platform, and is best suited to building Java projects.The most immediately noticeable difference between Ant and Make is that Ant uses XML to describe the build process and its dependencies, whereas Make uses Makefile format. By default the XML file is named build.xml.

5.2 Suitability of the tool(s)

Visual Studio includes a debugger that works both as a source-level debugger and as a machinelevel debugger. It works with both managed code as well as native code and can be used for debugging applications written in any language supported by Visual Studio. In addition, it can also attach to running processes and monitor and debug those processes. If source code for the running process is available, it displays the code as it is being run. If source code is not available, it can show the disassembly. The Visual Studio debugger can also create memory dumps as well as load them later for debugging. Multi-threaded programs are also supported. The debugger can be configured to be launched when an application running outside the Visual Studio environment crashes. The debugger allows setting breakpoints (which allow execution to be stopped temporarily at a certain position) and watches (which monitor the values of variables as the execution progresses). Breakpoints can be conditional, meaning they get triggered when the condition is met. Code can be stepped over, i.e., run one line (of source code) at a time. It can either step into functions to debug inside it, or step over it, i.e., the execution of the function body isn't available for manual inspection. The debugger supports Edit and Continue, i.e., it allows code to be

SDLC Report for Call Tracker Application

Page 12

edited as it is being debugged (32 bit only; not supported in 64 bit). When debugging, if the mouse pointer hovers over any variable, its current value is displayed in a tooltip ("data tooltips"), where it can also be modified if desired. During coding, the Visual Studio debugger lets certain functions be invoked manually from the Immediate tool window. The parameters to the method are supplied at the Immediate window.

5.3 Adoption of the Tools

Visual Studio includes a host of visual designers to aid in the development of applications. These tools include:

5.3.1 Windows Forms Designer

The Windows Forms designer is used to build GUI applications using Windows Forms. Layout can be controlled by housing the controls inside other containers or locking them to the side of the form. Controls that display data (like textbox, list box, grid view, etc.) can bebound to data sources like databases or queries. Data-bound controls can be created by dragging items from the Data Sources window onto a design surface.[31] The UI is linked with code using an event-driven programming model. The designer generates either C# orVB.NET code for the application.

5.3.2 Web Development

Visual Studio also includes a web-site editor and designer that allows web pages to be authored by dragging and dropping widgets. It is used for developing ASP.NET applications and supports HTML, CSS and JavaScript. It uses a code-behind model to link with ASP.NET code. From Visual Studio 2008 onwards, the layout engine used by the web designer is shared with Microsoft Expression Web. There is also ASP.NET MVC support for MVC technology as a separate download and ASP.NET Dynamic Data project available from Microsoft.

5.4 Outcome of this Activity

The outcome of the above are the ASP pages which include c# as its back end and the data base used is Sql Server Management Studio while the actual application is run by Microsoft Visual Studio 2010.

SDLC Report for Call Tracker Application

Page 13

The above two screenshots represent the application with which the Microsoft Visual Studio outputs the application.One of them is the login page and the other one is the default or the starting page in which the query of the customer is taken into account.When the customer gets the call or the customer calls for the problem to be solved then these things are taken into consideration. The call reason in terms of one,two and three are noted .The main call reason which can be helpful for the feedback of the application user.the resolved dropdown .the escalated radio button is also marked to know whether it is done or not.The transfer is also noted and if the transfer is done then the bank where these things are transferred are also noted and then checked for the

SDLC Report for Call Tracker Application

Page 14

conferencing . After the conferencing is done with no problem to the customer,the Dead air or No caller is checked . The database comes into picture later on when the query is known and the product to be retrieved is given .The known database is first filled with the data given by the organization in the requirement document (which is attached at the end of the document in the Appendix).The database queiries are then performed and the required data are then retrieved from the data base.The screenshots of the database are now given as under.

6. Testing
The testing phase can be done using manual testing in which all the test cases are generated by the tester and then the application is run .Testing can also be done by using any testing tool the tool used here is selenium.

6.1 Testing Method(s) Used

Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

SDLC Report for Call Tracker Application

Page 15

6.1.1 Methods of Testing

Methods involved in testing are: Manual Testing by generating scripts or by writing the test cases through which we can check by running the application. The test cases are developed with the help of validations used in the application The scripts for the tools is also developed with the help of the validations like form validation,password validation etc.

6.2 Tool(s) and its Features

6.2.1 Tools Used
The tool used apart from manual testing is Selenium. Selenium IDE is a complete integrated development environment (IDE) for Selenium tests. It is implemented as a Firefox Add-On, and allows recording, editing, and debugging tests. It was previously known as Selenium Recorder. Selenium-IDE was originally created by Shinya Kasatani and donated to the Selenium project in 2006.Scripts may be automatically recorded and edited manually providing autocompletion support and the ability to move commands around quickly. Scripts are recorded in Selenese, a special test scripting language for Selenium. Selenese provides commands for performing actions in a browser (click a link, select an option), and for retrieving data from the resulting pages.

6.2.2 Features
6.2.2.1 Selenium Grid Selenium Grid is a server that allows tests to use web browser instances running on remote machines. With Selenium Grid, one server acts as the hub. Tests contact the hub to obtain access to browser instances. The hub has a list of servers that provide access to browser instances (WebDriver nodes), and lets tests use these instances. Selenium Grid allows running tests in parallel on multiple machines, and to manage different browser versions and browser configurations centrally (instead of in each individual test). 6.2.2.2 Selinium Client API As an alternative to writing tests in Selenese, tests can also be written in various programming languages. These tests then communicate with Selenium by calling methods in the Selenium Client API. Selenium currently provides client APIs for Java, C#, Ruby and Python.With Selenium 2, a new Client API was introduced (with WebDriver as its central component). However, the old API (using class Selenium) is still supported.

6.2.2.3 Selinium IDE Selenium IDE is a complete integrated development environment (IDE) for Selenium tests. It is implemented as a Firefox Add-On, and allows recording, editing, and debugging tests. It was previously known as Selenium Recorder. Selenium-IDE was originally created by Shinya Kasatani and donated to the Selenium project in 2006.Scripts may be automatically recorded and edited

SDLC Report for Call Tracker Application

Page 16

manually providing autocompletion support and the ability to move commands around quickly.Scripts are recorded in Selenese, a special test scripting language for Selenium. Selenese provides commands for performing actions in a browser (click a link, select an option), and for retrieving data from the resulting pages.

6.3 Suitability of the Tool(s)

Call Tracker application makes use of testing in many ways . The selenium generates test cases which are then run by running the application. In this application the dropdown checks are done. The change in one dropdown with respect to the other is checked. The proper editing of int,float and string are took into concern. The tracker admin and the tracker customer records and their updates are checked.

6.4 Adoption of the Tool(s)

Selenium WebDriver is the successor to Selenium RC. Selenium WebDriver accepts commands (sent in Selenese, or via a Client API) and sends them to a browser. This is implemented through a browser-specific browser driver, which sends commands to a browser, and retrieves results. Most browser drivers actually launch and access a browser application (such as Firefox or Internet Explorer); there is also an HtmlUnit browser driver, which simulates a browser using HtmlUnit.Unlike in Selenium 1, where the Selenium server was necessary to run tests, Selenium WebDriver does not need a special server to execute tests. Instead, the WebDriver directly starts a browser instance and controls it. However, Selenium Grid can be used with WebDriver to execute tests on remote systems.

6.5 Outcome of this Activity

The Outcome of Testing can be categorized as following:1. 2. 3. 4. The Testing phase involves the generation of test cases. These test cases are checked by running the application. The outcome is that there might be any dis-satisfaction of the requirement document. The requirement document is completely checked and all the requirements are to be satisfied. Selenium testing phase include the generation of scripts as :-

SDLC Report for Call Tracker Application

Page 17

7. Software Project Management

7.1 Software Project Management Activities Followed
The Software Project management activities include: I. Project planning. II. Project scheduling III. Cost Estimation IV. Task Management

7.2 Tool(s) and its Features

7.2.1 Project Libre
Project Libre is free open-source software for planning and controlling projects. This project management software, which was developed using Java, is the successor of the legendary Freeware OpenProj.

7.3 Suitability of the Tool(s)

Project Libre being Open Source and freeware suited our project the most. Following are the functionalities provided by Project Libre which we have used in our application:

Project planning: Allows to create different projects and different stages in the particular project . Task management: Allows for the creation and assignment of tasks, deadlines and status reports. Calendar and contact sharing: Project timelines include scheduled meetings, activity dates and contacts which automatically updates across all stages and stakeholder calendars. Bug and error management: Allows to keep a track of software bug and error reporting, viewing, notifying and updating. Time tracking: Gantt Chart representation helps in tracking the overall time taken by each step of the development process. Cost Estimation : It allows to assign costs to various steps of the development process which helps in better cost estimation results and it allows takes account of the estimated cost and the actual cost hence providing a accurate cost estimation at the end of the software development cycle.

SDLC Report for Call Tracker Application

Page 18

7.4 Adoption of the Tool(s)

Using the Project Libre tool, we created a project plan initially i.e creating a separate entry for each level of the development and assigning a estimated cost for each level. Then deadlines were assigned to each step in the development process and work for the respective level was done accordingly.

7.5 Outcome of this Activity

SDLC Report for Call Tracker Application

Page 19

Appendix A: SRS Documentation

The following are required to gain the proper knowledge of the srs specification document Purpose of Call Tracker. Inteded Audience of the Application. Overall Description and External Interface Requirements. System Features. Other Non-Functional Requirements of the Call Tracker. srs_tem_call_tracker.pdf

Appendix B: Development Tools

The Development Tools can be : C#.NET,VB.NET Microsoft Visual Studio 2010,Microsoft Visual Studio 2012 Microsoft Sql Server Management Studio.

Appendix C: Test Cases / Test Reports

The test cases can be done with help of mapping as in the following figures:

SDLC Report for Call Tracker Application

Page 20