Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1. PROJECT ABSTRACT
The aim of this project is to develop an e-government website. This project is designed to
address the needs of government officials seeking to implement e-government projects,
or those already involved with such venture. It outlines key strategic issues that need to
be considered and addressed in the implementation of technology based e-government
initiatives.
This project deals with the automation of governmental tasks like birth registration, death
registration, issuing of birth and death certificates etc.
The other intention of creating this project is to provide the administrator over the full
authentication of allotting the different types of license to the different customers, death
& birth registration, financial services etc. The following are the tasks performed by the
system:
The main idea to develop this project is to provide the administrator a very light and easy
way to handle his all the customers and providing them a very easy way to get the
license.
License Module
Birth registration
Death registration
Issue birth & death certificate
Search details
Customer entry.
Details of customer
Type of license
Category description.
For which category the customer is applying for:
PFA
NPFA
ANIMAL
The software to be developed will include the information regarding the customers as
their type of license, date of issuing and renewal of license, record of birth & death of the
public etc.
Using World Wide Web portals to create one-stop shops is one currently popular e-
government approach to improving the delivery of public services to citizens. The basic
idea of these portals is to provide a single, convenient place to take care of all the steps of
a complex administrative process involving multiple government offices, bringing the
services of these offices to the citizen instead of requiring the citizen to run from office to
office.
Web portals can deliver government services with various levels of interaction. Three
levels are usually identified: information, communication, and transactions. Information
services deliver government information via static web pages and pages generated from
databases to citizens, tourists, businesses, associations, public administration, and other
government users. Communication services use groupware technology such as e-mail,
discussion forums and chat to facilitate dialogue, participation and feedback in planning
and policy-making procedures. Transaction services use online forms, workflow and
payment systems to allow citizens and business partners to take care of their business
with government online. Typical applications of transaction services for citizens include
applying for social benefits, registering automobiles, filing changes of address or
applying for building permits. For businesses, perhaps the application of greatest current
interest is the online procurement of government contracts.
Mobile2Win and Altruist Technologies are Value Added Service and Software Design &
Development Company with 450+ Employees Nationwide. They provide End to End IT
Solution for Domestic and Overseas Clients. Below given is the brief profile of our
Offered Services and Clients. We are looking for a chance to assist you with our technical
expertise in any of the below given Service area.
Mobile2WinAltruist group are a $40 Million company. We offer a wide range of WEB
and WAP related services such as Software application development, Website/Wapsite
design and development, Customized Windows applications, SEO, E-Commerce/M-
Commerce solutions. Below given is the range of our expertise we offer:
M2W-Altruist has always been at the leading edge of driving innovation in the IT
development industry. Our record is at adding value to our services through reduced time
to market, high quality, and technologically innovative processes. We are the technical
leader in our arena with over 450 experts hailing from engineering, technical and
management backgrounds devoted towards supplementing their knowledge with internal
research and development to ensure seamless delivery. We implement a powerful set of
proven techniques that assure quality and confidence in the design, construction, and
deployment of business applications. Below given is the set of technologies we deploy:
Application Development:
ASP.NET, VC#.NET, VB.NET, VC.NET, C++, PHP, Joomla, Java, J2EE, J2ME,
AJAX, iphone
Web Development:
Joomla 1.0, Joomla 1.5, VirtueMart, HTML, DHTML, XHTML, WORDPRESS,
Megento, Custom CMS, UltraDev, Visual Interdev, JavaScript, Zend Studio,
VBscript, Shopping Gateway Integration, PayPal, Authorize.NET, Google MAPS.
PSD to Templates, Joomla Templates, CSS 2.0 Templates, Meg
Designing:
Adobe Photoshop, Image Ready, Flash, CorelDraw, Photoshop and Fireworks.
Operating Systems:
Windows 2003 .NET Server, Windows 98/ME/XP/Vista and NT 2000, Linux and
Unix.
www.txt2mkts.com
www.eworldtradefair.com
www.property4delhi.com
www.chiragjoshi.com
www.anantassociates.com
http://jaconsultants.net
www.palmjewellery.com
www.altruistindia.com
www.jobsonphone.com
www.indiamobilechat.com
www.86serving.com
www.mchat.co.in
www.jumbosearch.co.uk
wap.Setindia.com
wap.Hindustantimes.com
wap.motozone.co.in
wap.cartoonnetwork.in
http://ac2.mobile2win.com/wapchat/idea
http://servercnt1.mobile2win.com/telcospecials/
http://servercnt1.mobile2win.com/mcard/home.aspx
m.mobile2win.com
lifeonmobile.in
Mobile2Win has an extensive background in developing Mobile Games and Applications.
Weve developed more than 1000 Mobile Games and application on J2ME and other
platform.
Mobile2Win and Altruist have a Strong tale of Top Brand Clients to whom we are
providing our services in various domains. Few World Known Clients are given below:
Altruist and Mobile2win are providing their value added services to all the leading
telecom operators not limited to Airtel, Vodafone, Idea, Tata, Aircel, MTNL, BSNL and
Reliance.
The aim of this project is to develop an e-government website. This project is designed to
address the needs of government officials seeking to implement e-government projects,
or those already involved with such venture. It outlines key strategic issues that need to
be considered and addressed in the implementation of technology based e-government
initiatives.
Birth Registration
Death Registration
State Details
Hospital Details
Add New State & Hospital
Issue Birth & Death certificate
Birth & Death details search
Customer entry.
Category description.
The project is to computerize the working of government officials. The manual system of
government tasks such as registration of birth and death, registration of customers
applying for license for opening new shop which may be pure food or non pure food etc.
takes lot of time and has lot of paper work. Due to this lot of time is wasted and
processing speed and data entering speed became very slow.
Therefore need for computerization not due to the large volume of data transactions are
taking place, but to maintain the integrity of data. Some data has to re-write in various
files due to which it is possible for error to creep in. This type of errors are difficult to
find, as it requires comparing four-five files which leads to wastage of time and
manpower . But with the use of this software these kinds of inconsistencies can be
avoided, because it informs the moment the error is committed, thus the data integrity is
maintained.
In the existing system all the work from addition of new records to modifying is done
manually. During customer entry, the first step is to fill up details about him like his
name, father name, address, type of license applying for, details of certificate required to
issue a license etc. takes a lot of time then license no. allocated must be entered in the
register manually which again consume a lot of time and space. The means for reading
and gaining knowledge is books i.e. frustrating to both user and client.
With the use of this software reports can be generated very easily and instantly where as
using manual system it takes lot of time to generate reports. It is possible that user may
leave empty or different records for same fields in different files but through this software
such kind of errors cant creep in.
4.2) Maintenance:
Maintaining record in excel sheets is not so easy.
4.3) Upadation:
It is difficult to change or update the records.
4.4) Complexity:
Complexity of information handling and the gathering and determination of
information is usually the most difficult problem faced.
Maintaining separate files for each department can lead to duplication of data
present in files. This can lead to:
.a Inconsistencies
.b Update anomalies
.c Decentralization problems
Human kind of errors may be generated in typing errors and slow arithmetic
calculations, fatigue and boredom.
4.7) No Security:
In case of manual work, security of data cannot be maintained.
The proposed system is to centralize all the work so that it can be managed easily by the
company and also it can be easily accessed by the resources working for the company.
The proposed system is software, which is expected to remove the problems of the
existing system and provide value added solutions to the problems faced by the current
system.
5. SYSTEM REQUIREMENTS
The main purpose of the product specification is to define the need of the products user.
Sometimes, the specification may be a part of a contract sign between the producer and
the user. It could also form part of the user manuals. A users needs are sometimes not
clearly understood by the developer. If this is the case, a careful analysis involving
many interactions with the user should be devoted to reaching a clear statement of
requirements; in order to avoid possible misunderstandings.
Sometimes, at the beginning of a project, even the user has no clear idea of what exactly
the desired product is. Think for instance of user interface , a user with no previous
experience with computer products may not appreciate the difference between , say
menu driven interaction and a command line interface. Even an exact formation of
system functions and performance may be missing an initial description produced by an
inexperienced user.
With project the government can manage data more easily. For this the system has been
analyzed and clearly understood. We are required to make this computerized and also
provide online access of the connection to the resources.
Technology Used:
Database Used
The strategy for the system involved studying about the system, stating the problem and s
olutions to be provided, determining requirements, hardware, software etc. The team me
mbers sat together, discussed the problem, studied the system, gathered information abou
t the type of data used in the system, the flow of data, understood the users requirements
and determine how to solve the problems. The team leader decided to use spiral model.
After developing a simple solution of the problem, a demo of the developed project is
given to the user and according to his requirements more functionality is added to the
project.
Acceptance criteria are the key to making sure our stories are done, and have as few bugs
as possible. When the criteria are weak, not complete, unclear or misunderstood, this can
be the root of a whole host of problems.
the Developers, and the QA people on the team should all be in agreement that the
acceptance tests do illustrate that the software works as desired.
Acceptance criteria can be a tricky bit, especially if the customer and the team don't have
much experience at generating and capturing them. I would definitely consider it a
process smell if I saw a continuing pattern of low quality acceptance criteria. thus the
acceptance criteria play a vital role. Really this can kill a project if left untended to fester
on its own. From what I have seen on several teams, we should all focus more time and
effort on acceptance criteria gathering and then automating it in the sprint as part of the
criteria for Done.
The next step in analysis is to verify the feasibility of the proposed system. "All projects
are feasible given unlimited resources and infinite time ". But in reality both resources
and time are scarce. Projects should conform to time bounds and should be optimal in
three consumption of resources. This places a constant on approval any project.
5.2.1 Purpose
The feasibility analysis is designed to determine whether or not, given the project
environment, a project will be successful (in virtually any interpretation of that word). A
feasibility analysis may be conducted for a project with an emphasis on financial
viability, environmental integrity, cultural acceptability, or political practicability. It is a
determination as to the likelihood of success and a description of how that determination
was achieved.
Feasibility analyses are used to present an approach or a series of alternatives and to offer
decision-making guidance based on the climate in which the project will evolve. They
often defend a single or primary approach, incorporating extensive forecasts on the
The team for developing Resource Tracker System is equipped with all the modern
facilities and the latest software. Therefore as far as the equipment and the software was
concerned there was no problem. Moreover the technical skills required to complete the
project were also present in the form of competent software professionals. Thus the
project was considered technically feasible.
Economic analysis is the most frequently used technique for evaluating the effectiveness
of a proposed system. More commonly known as cost/benefit analysis, the procedure is
to determine the benefits and saving that are expected from a proposed system and
compare them with cost. If benefits outweigh cost, a decision is taken to design and
implement the system. Otherwise, further justification or alternative in the proposed
system will have to be made if it is to have a chance of being approved. This is an
ongoing effort that improves in accuracy at each phase of the system life cycle.
The costs include development costs, equipment costs, personal costs like team members
salaries, operating costs like power used etc. Since, the benefits and savings overweigh
costs, a decision is made to design and implement the system.
Proposed system is beneficial only if they can be turned into information system that will
meet the organization operating requirements and efficiency. As the system is user
friendly for those who have to maintain the records of work done on each project by
various resources and also to resources that have to make their day to day time entries. If
the user wants more facilities that can also be provided
The team structure was of hierarchical type. The authorities and delegations were divided
in the hierarchical way. It followed Top to Bottom approach.
In this project there is one Program Manager, one Project Manager, one Technical Leader
and one Senior Software Engineer. Seven trainees are allotted for this project and project
is progressed under the supervision of all the team members.
Program Manager
Project Manager
Technical Lead
Software Engineer
Trainee Trainee
Trainee
We are divided into different teams. Each team has been assigned its own module, and in
team we are assigned sub modules to different members.
At first stage we are asked to analysis our sub module requirements.
Then we were asked to make our sub modules database as well as data flow diagrams.
The DFDs well as database designed by us were checked and modified by the experts.
Finally we were asked to design our database in SQL SERVER 2005
After designing our database we are ask to design front end in asp.net.
After designing here arise the most critical phase that is coding.
Programming language and development tools:-We are working with the .net framework
and project will be developed in asp.net which will be at front end and we are using SQL
SERVER 2005 as backend.
5.3.3.2 ASP.NET
CHARACTERISTICS
PAGES
.NET pages, known officially as "web forms", are the main building block for application
development.[8] Web forms are contained in files with an ".aspx" extension; in
programming jargon, these files typically contain static (X)HTML markup, as well as
markup defining server-side Web Controls and User Controls where the developers place
all the required static and dynamic content for the web page. Additionally, dynamic code
which runs on the server can be placed in a page within a block <% -- dynamic code
-- %> which is similar to other web development technologies such as PHP, JSP, and
ASP, but this practice is generally discouraged except for the purposes of data binding
since it requires more calls when rendering the page Note
USER CONTROLS
ASP.NET supports creating reusable components through the creation of User Controls.
A User Control follows the same structure as a Web Form, except that such controls are
derived from the System.Web.UI.UserControl class, and are stored in ASCX files. Like
ASPX files, an ASCX file contains static HTML or XHTML markup, as well as markup
defining web control and other User Controls. The code-behind model can be used.
Programmers can add their own properties, methods, [9] and event handlers.[10] An event
bubbling mechanism provides the ability to pass an event fired by a user control up to its
containing page.
User can also build Custom Controls for Asp.Net application. Where controls are in
compiled DLL file. And by using Register directive user can use control from DLL.
RENDERING TECHNIQUE
After the request has been processed, the instance of the page class is discarded and with
it the entire control tree.
STATE MANAGEMENT
ASP.NET applications are hosted in a web server and are accessed over the stateless
HTTP protocol. As such, if the application uses stateful interaction, it has to implement
state management on its own. ASP.NET provides various functionality for state
management in ASP.NET applications.
TEMPLATE ENGINE
When first released, ASP.NET lacked a template engine. Because the .NET framework is
object-oriented and allows for inheritance, many developers would define a new base
code with markup. Furthermore, this method can only be visually tested by running the
application - not while designing it. Other developers have used include files and other
tricks to avoid having to implement the same navigation and other elements in every
page.
ASP.NET 2.0 introduced the concept of "master pages", which allow for template-based
page development. A web application can have one or more master pages, which can be
nested.[14] Master templates have place-holder controls, called Content Placeholders to
denote where the dynamic content goes, as well as HTML and JavaScript shared across
child pages.
Child pages use those ContentPlaceHolder controls, which must be mapped to the place-
holder of the master page that the content page is populating. The rest of the page is
defined by the shared parts of the master page, much like a mail merge in a word
processor. All markup and server controls in the content page must be placed within the
ContentPlaceHolder control.
When a request is made for a content page, ASP.NET merges the output of the content
page with the output of the master page, and sends the output to the user.
The master page remains fully accessible to the content page. This means that the content
page may still manipulate headers, change title, configure caching etc. If the master page
exposes public properties or methods (e.g. for setting copyright notices) the content page
can use these as well.
Data Tier is basically the server which stores all the applications data. Data tier
contents Database Tables, XML Files and other means of storing Application
Data.
Business Tier is mainly working as the bridge between Data Tier and Presentation
Tier. All the Data passes through the Business Tier before passing to the
presentation Tier. Business Tier is the sum of Business Logic Layer, Data Access
Layer and Value Object and other components used to add business logic.
Presentation Layer
Presentation Layer is the only layer which is directly connected with the user. So in this
matter, its also a really important layer for marketing purposes. Presentation Layer is
mainly used for getting user data and then passing it to Business Logic Layer for further
procedure, and when data is received in Value Object then its responsible to represent
value object in the appropriate form which user can understand.
SQL SERVER
Microsoft SQL Server is an application used to create computer databases for the
Microsoft Windows family of server operating systems. It provides an environment used
to generate databases that can be accessed from workstations, the web, or other media
such as a personal digital assistant (PDA). Microsoft SQL Server is probably the most
accessible and the most documented enterprise database environment right now.
products for this market segment. SQL Server is easy to manage and provides a separate
OLAP engine. Porting it to other platforms has been disclosed.
* INTERNET INTEGRATION
The SQL Server 2000 database engine includes integrated XML support. It also has the
scalability, availability, and security features required to operate as the data storage
component of the largest Web sites. The SQL Server 2000 programming model is
integrated with the Windows DNA architecture for developing Web applications, and
SQL Server 2000 supports features such as English Query and the Microsoft Search
Service to incorporate user-friendly queries and powerful search capabilities in Web
applications.
The same database engine can be used across platforms ranging from laptop computers
running Microsoft Windows 98 through large, multiprocessor servers running
Microsoft Windows 2000 Data Center Edition. SQL Server 2000 Enterprise Edition
supports features such as federated servers, indexed views, and large memory support
that allow it to scale to the performance levels required by the largest Web sites.
The SQL Server 2000 relational database engine supports the features required to support
demanding data processing environments. The database engine protects data integrity
while minimizing the overhead of managing thousands of users concurrently modifying
the database. SQL Server 2000 distributed queries allow to reference data from multiple
mobile, disconnected users, have them work autonomously, and then merge their
modifications back to the publisher.
SQL Server 2000 includes a set of administrative and development tools that improve
upon the process of installing, deploying, managing, and using SQL Server across several
sites. SQL Server 2000 also supports a standards-based programming model integrated
with the Windows DNA, making the use of SQL Server databases and data warehouses a
seamless part of building powerful and scalable systems. These features allow to rapidly
deliver SQL Server applications that customers can implement with a minimum of
installation and administrative overhead.
AJAX is not a new programming language, but a technique for creating better, faster, and
more interactive web applications.With AJAX, your JavaScript can communicate directly
with the server, using the JavaScript XMLHttpRequest object. With this object, your
JavaScript can trade data with a web server, without reloading the page.
AJAX uses asynchronous data transfer (HTTP requests) between the browser and the
web server, allowing web pages to request small bits of information from the server
instead of whole pages.The AJAX technique makes Internet applications smaller, faster
and more user-friendly.AJAX is a browser technology independent of web server
software.
Brief history
Ajax is only a name given to a set of tools that were previously existing. The main part is
XMLHttpRequest, a server-side object usable in JavaScript, that was implemented into
to the success of this format. But this is the when the name Ajax was itself coined that the
technology started to be so popular.
What is Ajax?
If you've surfed the web at all lately, most likely you've seen Ajax in action without
realizing it. Ajax can help increase the speed and usability of an application's web pages
by updating only part of the page at a time, rather than requiring the entire page to be
reloaded after a userinitiated change. Through the power of Ajax, the pages of your
application can exchange small amounts of data with the server without going through a
form submit. The Ajax technique accomplishes this by using the following technologies:
JavaScript that allows for interaction with the browser and responding to events
The DOM for accessing and manipulating the structure of the HTML of the page
XML, which represents the data passed between the server and client.
An XMLHttpRequest object for asynchronously exchanging the XML data between
the client and the server.
The following graphic shows how these technologies work together to update a piece of a
page with new data from the server.
The main purpose of Ajax is to provide a simple and standard means for a web page to
communicate with the server without a complete page refresh. To illustrate this, consider
a simple registration form. You have very likely experienced the frustration of having to
try multiple usernames when registering for some new website. You fill out the entire
form, hit the submit button, wait for a second or so, and then get the same form right back
with a message saying that the username you have chosen is not available. You try
another easy-to-remember username and find it is also not available. You repeat this
several times until finally you pick some obscure username. This process wouldn't be
nearly as bad if you didn't have to wait for the entire page to refresh each time you tried a
new username. But that's a very simple example. Some web-based applications require
constant interaction with a database through a middle-tier. Take, for example, an interface
for updating employee records. The traditional way of doing this is illustrated below.
Following is a template for the RS document. Some example requirements are entered in
to it to show how to use the template. Make sure that you enter even the smallest/most
trivial requirements also. That would help in validating the system during testing.
In the late 1970s data-flow diagrams (DFDs) were introduced and popularized for
structured analysis and design (Gane and Sarson 1979). DFDs show the flow of data
from external entities into the system, showed how the data moved from one process to
another, as well as its logical storage.
There are several common modeling rules that I follow when creating DFDs:
LEVEL 1
LEVEL 1
7. DESIGN
7.1 Database Design:
Objectives of Database
Controlled redundancy
Redundancy data occupies space and therefore, is wasteful. If versions of the same
data are in different phases of updating, the system often gives conflicting
information. A unique aspect data base design is storing only once, which controls
redundancy and improves system performance.
Data Integration
It refers to the fact that the data is stored physically at different locations, but
logically the information is centralized.
Data Integrity
Data Integrity means storing all the data. This leads to more consistency, less
redundancy and reduces direct access storage requirement.
Data Independence
Description: This table is used to store details of the customer who want to apply for a
license
Description: This table is used to store information about the type of the license
Description: This table is used to enter store the description of the license
Description: This table is used to store information about Animal type of license which
is issued to customers
Description: This table is used to store the information about the documents required for
the issue of the license
Description: This table is used to store the information about fee for each type of license
Description: This table is used to store information about the users of the application.
New Users created are stored in this table.
Description: The information about modules of the application is stored in this table.
Description: The information about form name, form description of each module is
stored in this table.
Description: The information about which user can access which module is stored in
this table.
Description: This table stores information about the forms of particular module which
are accessible to the user of the application. Each user is checked for the permission of
the form he is going to open from this table.
Description: This table stores the departments i.e. department name and department id.
Description: This table stores information about the various designations in each
department.
7.2.1 frmLoginpage.aspx
This page is the first page of license module .here, user can logged on to the license
module. This provides the security as the password of the user saved in the database in
encrypted form. The user of the license module is created by the administrator through
the admin module.
This is the welcome page of the application. User is redirected to this page after
successful login.
Financial year master is the master where the current financial year is set.
Customer entry is the master where all the entries regarding customer is saved in the
database .the customer entries can be their ward like Rajpura, Patiala, etc., their name,
age, address. The data regarding customers can be manipulated i.e. updating, deletion can
be done.
7.2.5 frmCategoryDesc.aspx
Category description is the next master where the categories are added. These
categories are the applications for license on which user will issue license. The
categories are PFA (Pure Food Application), NPFA (Non Pure Food Application),
Animal. Editing of this category description can also do here.
7.2.6 frmSubCategoryDesc.aspx
7.2.7 frmApplyPFA.aspx
The user can apply for license for the pure food from this form. The application can
be for new license or it can be for renewal of existing license. The user has to enter
the type whether it is new or renew. Then the user will enter the financial year, current
receipt number. If the user selected new then it will further enter all the details of the
customer like ward, customer id, name, address, pure food, trade. Then he will enter
the fee and the documents for the license. But, if he entered the type renew, then he
will enter the old receipt number of the applicant and all details are automatically
filled and the license will renewed.
7.2.8 frmApplyNpfa.aspx
The user can apply for license for the non pure food from this form. The application
can be for new license or it can be for renewal of existing license. The user has to
enter the type whether it is new or renew. Then the user will enter the financial year,
current receipt number. If the user selected new then it will further enter all the details
of the customer like ward, customer id, name, address, non pure food, trade. Then he
will enter the fee and the documents for the license. But, if he entered the type renew,
then he will enter the old receipt number of the applicant and all details are
automatically filled and the license will renewed.
7.2.9 frmAnimal.aspx
The user can apply for license for the animal from this form. The application can be
for new license or it can be for renewal of existing license. The user has to enter the
type whether it is new or renew. Then the user will enter the financial year, current
receipt number and token. If the user selected new then it will further enter all the
details of the customer like ward, customer id, name, address and the details of the
animal i.e. animal name, breed, sex, vaccination, vaccination date, vaccination marks.
Then he will enter the fee and the documents for the license. But, if he entered the
type renew, then he will enter the old receipt number of the applicant and all details
are automatically filled and the license will renewed.
7.2.10 frmIssue.aspx
Here, the license is issued to the customer. The user will enter all the details before
issuing the license i.e. ward, category description, financial year, applicant number,
current receipt number, apply date , total fees etc . Then the license would issue to the
customer.
7.2.11 frmLicDocs.aspx
The next master is the documents update. Here the documents are added which are
required for license. These documents can be different for different application of license.
The documents can be birth certificate, NOC (No Objection Certificate) , residence
certificate. These documents can be updated in this master.
7.2.12 frmupdatefee.aspx
Fee update is the master for fee. The fee for Pure Food Application, Non Pure Food
Application, and Animal would be different. The user will select the type of license
and then enter the fee for respective license type.
7.2.13 createuser.aspx
This form is used by admin to create new users of the application.User ID is auto
generated and passwords are stored in encrypted form.
7.2.14 Changepassword.aspx
7.2.15 frmAdminUserAuthorisationMod.aspx
This form is used to give permissions to user to access particular module of the
application. If admin wants to remove the permissions of any user then it is also done
through this form.
7.2.16 frmAdminUserAuthorisationForms.aspx
This form is used to give permissions to user to access forms of a particular module i.e.
which form of which module are accessible by the user .Permission pupation is also done
through this form.
7.2.16 frmNewModForm.aspx
This form is used by admin if in future any new module or form in an existing module is
added. Admin use this form to enter these new modules or forms.
8. TEST PLAN
The testing activities are done in all phases of the lifecycle in an iterative software
development approach. However, the emphasis on testing activities varies in different
phases. This procedure explains the focus of testing in inception, elaboration,
construction and transition phases. In the inception phase most of requirements capturing
is done and the test plan is developed. In elaboration phase most of design is developed,
and test cases are developed. Construction phase mainly focuses on development of
components and units, and unit testing is the focus in this phase. Transition phase is about
deploying software in the user community and most of the system testing and acceptance
testing is done in this phase.
Purpose
Test Planning
Initial test plan addresses system test planning, and over the elaboration, construction and
transition phases this plan is updated to cater other testing requirements of these phases,
like, unit & integration testing. The test Plan must contain the following:
Scope of testing
Test cases describe the details of every test for each feature of the module. The inputs for
preparation of test cases are the software requirement specifications and/or Design
document/model. System test cases are prepared in elaboration phase, and initial
integration test cases are prepared which are refined and completed in construction phase.
These test cases are reviewed as per Review Procedure as defined by the Project Manager
and adequate review records are maintained. These reviews are done against
requirements and Design to ensure adequacy and completeness.
The expected results are specified in test cases, against test to be carried out.
One of the test cases made for the Registration module is shown next.
An Acceptance Plan is prepared and handed over to the customer. However it is at the
discretion of the Project Manager to decide when to prepare the Acceptance Plan but the
Project Manager should ensure that it is at least prepared before the completion of
construction phase.
This Plan helps the customer in planning, scheduling and providing resources to carry out
the customer acceptance testing. The acceptance testing is done during deployment.
The Acceptance plan must consist of:
A suggested schedule for Acceptance Testing by the customer
Unit Testing
I n t e g r a t i o n Tes t i n g
The system integrator compiles and links the system in increments. Each increment needs
to go through testing of the functionality that has been added, as well as all tests the
previous builds went through (regression tests). Within an iteration, integration testing is
executed several times until the whole system has been successfully integrated.
Testing is done as per the Test Plan for the project. A Testing Team who may be an
independent team or may include members of the project team carries out the tests.
S y s t e m Tes t i n g
System testing is initiated through a System release and a Release Note from
Development team to the testing team. The purpose of the System Testing is to ensure
that the complete system functions are intended. The system roles in PMP compile and
link the system in increments.
System Testing is similar to the Integration testing except that it is run under customer
environment or in an environment as similar as to the customer environment, as possible.
During the System testing the performance criteria is tested and factors like stress,
transaction timing, volume of data, transaction frequency etc. are validated. The ability of
the Software to be installed in an environment likely to be encountered at the site of the
customer is also checked here.
Unit Testing:
In unit testing different modules are tested against the specification produced during
design for the modules. Unit testing is for verification of the code produced during the
coding phase, and hence the goal is to test the internal logic of the modules.
Integration Testing:
In this, many units tested modules are combined into subsystems, which are then tested.
The goal here is to see if the modules can be integrated properly. Hence, the emphasis is
on testing interfaces between modules. This testing activity can be considered testing the
design.
Pre-Acceptance Testing:
Acceptance testing is running the system with live data by the actual. It is performed
with realistic data of the client to demonstrate that the software is working satisfactorily.
It is performed when some changes are made up to an existing system. A change is made
to up grade the software by adding new features and functionality. The modified
software needs to be testing to make sure that new features to be added do indeed work.
Besides ensuring the desired behavior of the new services, testing has to sure that the
desired behavior of the old services is maintained. This is task of regression testing.
Validation Testing:
User input must be validated to conform to expected values. For example, if the software
program is requesting input on the price of an item, and is expecting a value such as 3.99,
the software must check to make sure all invalid cases are handled. A user could enter the
price as -1 and achieve results contrary to the design of the program. Other examples of
entries that be entered and cause a failure in the software include: 1.20.35, Abc,
0.000001, and 999999999. These are possible test scenarios that should be entered
for each point of user input. Typically when invalid user input occurs, the program will
either correct it automatically, or display a message to the user that their input needs to be
corrected before proceeding.
Stress Testing:
In software testing, stress testing refers to tests that determine the robustness of software
by testing beyond the limits of normal operation. Stress testing is particularly important
for mission critical software, but is used for all types of software. Stress tests
commonly put a greater emphasis on robustness, availability, and error handling under a
heavy load, than on what would be considered correct behavior under normal
circumstances.
Reasons for stress testing include:
1. The software being tested is mission critical, that is, failure of the software (such as
a crash) would have disastrous consequences.
2. The amount of time and resources dedicated to testing is usually not sufficient, with
traditional testing methods, to test all of the situations in which the software will be
used when it is released.
Performance Testing:
Performance testing can serve different purposes. It can demonstrate that the system
meets performance criteria. It can compare two systems to find which performs better. Or
it can measure what parts of the system or workload cause the system to perform badly.
In the diagnostic case, software engineers use tools such as profilers to measure what
9. IMPLEMENTATION
The term implementation has different meanings, ranging from the conversion of a basic
application to a complete replacement of a computer system. However the procedure is
almost similar. Implementation is used here to mean the process of converting a new or a
revised system design into an operational one. Conversion is one aspect of
In our case we are having third type of implementation in which we are replacing the
existing excel work in a web based centralized system. This type of implementation is
relatively easy as compared to other two.
This phase is less creative than design phase. It is primarily concerned with user training,
site preparation and file conversions. The final communications and links to other
modules and hardware components are established to make the software operative. After
that the program is run with live data otherwise a diagnostic
Procedure is used to locate and correct the errors in program. In most of the cases, a
parallel run is conducted where the new software runs simultaneously with the older one,
thats why software implementation includes the installation of original software and
made it operational in an operative environment. It continues until the software is
operating in accordance with the defined user requirements.
This system may require further advancements as the client may want some more
functionality in this system. While developing this project spiral model is followed so
coding is written in such a way that if client wants to add more functionality in this
system then that functionality can be done easily.
All members of the project team have to be cooperative with each other.
User should be given proper training about how to use project.
The primary concern of every system client is validity of the purchased software product
in the near future. In order to cope with this problem, programmers often provide their
clients with regular system updates so that in case there have been any change include in
working criteria of institution/organization, it can be absorbed within existing automated
system.
I have compiled this project keeping this point in full regards that it can be easily
upgraded if need arises. From time to time, new modules can be added to it or existing
ones can be modified. The development tools we have used i.e. Asp .Net MVC and LINQ
are flexibility allowing tools and hence changes to existing system can be made very
easily in order to make it serve a long way.
Depending upon the organization, the function processes and needs may vary from
organization to organization. Therefore, the functionality of the project can be further
enhanced as per the requirements specification of different organization. For instance, any
organization can use this project by just changing the interest rate accordingly and the rest
of the operations will be remained same. Similarly, the project can be expanded to the
required extent.
11. BIBLIOGRAPHY