report sample of asp project
DESCRIPTION
asp net sample projectTRANSCRIPT
INDEXSr.no Content Page No.
1 Introduction to Project or Product / Problem Assigned 11
2 Requirement Analysis :
Problem Analysis
15
3 Introduction to SRS(Software Requirement Specification)
Developing Tools
Hardware & Software requirement
19
4 General Descriptions of Project 27
5 Software Design
System Design
Architectural Design (i.e., DFD’s)
User Interface Design
Component Level/ Detailed Level Design
36
6 Coding
Approach used Top Down/Bottom up
41
7 Testing
Test Cases & Test Criteria
60
1 | P a g e
8 Implementation & Evaluation of Project
Containing maintenance measures
65
9 Conclusion and Scope of the project 69
10 Bibliography 73
Introduction to .NET
2 | P a g e
Project Description:-
Microsoft .Net Framework is a programming infrastructure created by Microsoft for
Building, deploying, and running applications and services that use .NET technologies,
Such as desktop applications and Web services.
The Microsoft .NET Framework is a software framework that can be installed on
Computers running Microsoft Windows operating systems. It includes a large library of
Coded solutions to common programming problems and a virtual machine that manages
The execution of programs written specifically for the framework.
FFFFFFFFF 3F5. .
Provides the first additions to the base class libraries to the .NET Framework since
Version 2.0.
Journey of .net framework
3 | P a g e
1F0. .
• The old .NET Framework logo
• This is the first release of the .NET Framework, released on 13 February 2002
• Available for Windows 98, NT 4.0, 2000, and XP.
• Mainstream support by Microsoft for this version ended 10 July 2007, and
Extended support ends 14 July 2009
FFFF FFFFFFFFF 1F1
• This is the first major .NET Framework upgrade.
• It was published on 3 April 2003. It is also part of the second release of Microsoft
Visual Studio .NET (released as Visual Studio .NET 2003).
• This is the first version of the .NET Framework to be included as part of the
Windows operating system, shipping with Windows Server 2003.
• Mainstream support for .NET Framework 1.1 ended on 14 October 2008, and
Extended support ends on 8 October 2013.
• Since .NET 1.1 is a component of Windows Server 2003, extended support for
.NET 1.1 on Server 2003 will run out with that of the OS - currently 30 June 2013.
1F1 FF FFFFFFFFFF FFFF 1F0. .
• Built-in support for mobile ASP.NET controls.
• Security changes - enable Windows Forms assemblies to execute in a semi trusted
Manner from the Internet, and enable Code Access Security in ASP.NET
Applications.
• Built-in support for ODBC and Oracle databases.
• .NET Compact Framework
• Internet Protocol version 6 (IPv6) support
.
4 | P a g e
FFFF FFFFFFFFF 2F0
• Released with Visual Studio 2005, Microsoft SQL Server 2005.
• It was published on 2006-01-22.
• It is included as part of Visual Studio 2005 and Microsoft SQL Server 2005.
• Version 2.0 is the last version with support for Windows 2000, Windows 98.
It shipped with Windows Server 2003 R2 (not installed by default).
FFFFFFF FF 2F0 FF
FFFFFFFFFF FFFF 1F1
• SQL Server Integration
• Full 64-bit support
• Language support for generics built directly into the .NET CLR.
• Anonymous Methods
• Null able Types
• Iterators
• Partial Classes
• New data controls with declarative data binding.
• New personalization features for ASP.NET, such as support for themes, skins
And web parts.
FFFF FFFFFFFFF 3F0
• .NET Framework 3.0, formerly called Win FX,
• includes a new set of managed code APIs that are an integral part of Windows
Vista and Windows Server 2008 operating systems.
• It is also available for Windows XP SP2 and Windows Server 2003 as a
Download.
• There are no major architectural changes included with this release.
5 | P a g e
FFFFFFF FFFFFFFFFFFF FFFFFFFFFF
( )
• Formerly code-named Avalon
• A new user interface subsystem
• API based on XML and vector graphics, which uses 3D computer graphics
Hardware and Direct3D technologies.
FFFFFFF FFFFFFFFFFFFF
FFFFFFFFFF FFFFF
• Formerly code-named Indigo
• A service-oriented messaging system which allows programs to interoperate
Locally or remotely similar to web services.
• is Microsoft's unified framework for building secure, reliable, transacted, and
Interoperable distributed applications.
FFFFFFF FFFFFFFF FFFFFFFFFF
FFFF
• allows for building of task automation and integrated transactions using
Workflows.
• It is the programming model, engine and tools for quickly building workflow
Enabled applications.
• WF radically enhances a developer’s ability to model and support business
processes.
FFFFFFF FFFFFFFFF
• Formerly code-named Info Card
• A software component which securely stores a person's digital identities and
Provides a unified interface for choosing the identity for a particular transaction,
Such as logging in to a website.
• In the physical world we use business cards, credit cards and membership cards.
6 | P a g e
Online with Card Space we use a variety of virtual cards to identify ourselves,
Each retrieving data from an identity provider.
FFFF FFFFFFFFF 3F5
• Version 3.5 of the .NET Framework was released on 19 November 2007, but it is
Not included with Windows Server 2008.
• As with .NET Framework 3.0, version 3.5 uses the CLR of version 2.0. In
Addition, it installs .NET Framework 2.0 SP1, .NET Framework 2.0 SP2 (with
3.5 SP1) and .NET Framework 3.0 SP1, which adds some methods and
Properties to the BCL classes in version 2.0
7 | P a g e
8 | P a g e
Introduction to Project
Introduction
FFFFFFFFFFFF:
This project work can be used in Sell anything from used cars to mobiles,
furniture, laptops, clothing and more. Submit ads for free and without
creating an account. If you want to buy something - here you will find
interesting items, cheaper than in the store. Start buying and selling in
the easiest way on SL.in. This application is very interactive one which itself explains
the user how to use it. To help the users, the software is also provided with user manual and help for
assisting the users to how to use this software. There is no paper-based record keeping. All the
records are mounted on the computer. All the calculations are automatically.
Presently, manual filing system is used at the Institute of Management Studies. In this system
a manual file is maintained for the applications received from the candidates. After the deadline for
receiving the applications the security of the applications are done, the applications found
incomplete in any form are rejected, like, percentage less than the required one, supporting
documents incomplete, false or not attached etc.
After the security of the applications a list of the valid applicants is made. Once the applicant
list is ready then a new list is made according to percentage received and this called as the merit list.
Based on this merit list admissions are done.
9 | P a g e
10 | P a g e
Profile Of Problem Assigned
Problem Assigned
This application is very interactive one which itself explains the user how to use it. To help the users,
the software is also provided with user manual and help for assisting the users to how to use this
software. There is no paper-based record keeping. All the records are mounted on the computer. All
the calculations are automatically.
FFF FFFFFFFFFF:
To provide such kind of platform where the Institute can increase their growth and market
strength through the optimization in time and man power with the help of proposed System. Also the
Institute can better target to their goals through the various types of reports and charts generated by
the system.
FFFFFFFFFFFFFFFF:
The main features of the project are as follows:
This will be Web based software.
Proposed Front end: ASP.Net 2008
Proposed Back end: MS SQL Server 2005
This will be monolingual software, which operates in English.
11 | P a g e
PROPOSED SYSTEM
12 | P a g e
Proposed System
OBJECTIVE
The objective of our project is to create a website through which organizing an event will become
easier and efficient with the help of latest tool of information and technology. It is very user friendly
website.
The basic objectives of the project are:
To have a feature which will help the user to ask any question related to their problem.
It is very user friendly.
It also provides user way to share their views.
The events like: add post, add questions, and add their replies.
All the posts of users are under check of admin.
If there is any post which is not appropriate, admin can delete or edit.
FFFFFFFF
Some features of our project are:
Easy to read.
Easy to navigate.
Comfortably viewed.
Clear and to the point.
Admin keep track of the module always.
Avoid dead links.
Clear and to the point.
Browser compatible.
13 | P a g e
Problem Analysis
14 | P a g e
Study of Existing System
The main goal of the on line Institute Management System is to provide such kind of platform where
the Institute can increase their growth and market strength through the optimization in time and man
power with the help of proposed system. Also the Institute can better target to their goals through the
various types of reports and charts generated by the system.
When we started the above problem following questions arises behind us:
How to Submit and execute record of Candidates.
How to prepare different types of screens for viewing record at any time.
How to maintain record of updated Candidates.
We will solve these problems by making a systematic study of these problems. We will solve
a complex problem breaking it into simple and easy to handle form.
15 | P a g e
16 | P a g e
Introduction to SRS
S o f t w a r e R e q u i r e m e n t S p e c i f i c a t i o n
( )
Developing Tools
17 | P a g e
MICROSOFT VISUAL STUDIO 2012
MICROSOFT SQL SERVER 2008
18 | P a g e
MICROSOFT VISUAL STUDIO 2008
19 | P a g e
MICROSOFT SQL SERVER 2005
DEVELOPING TOOLS
20 | P a g e
FFFFF FFF: ASP.NET
ASP.NET is a web application framework developed and marketed by Microsoft to allow
programmers to build dynamic web sites, web applications and web services. ASP.NET is an
entirely new technology for server-side scripting. It was written from the ground up and is not
backward compatible with classic ASP.ASP.NET is the major part of the Microsoft's .NET
Framework.
An ASP.NET file is just the same as an HTML file
An ASP.NET file can contain HTML, XML, and scripts
Scripts in an ASP.NET file are executed on the server
An ASP.NET file has the file extension ".aspx"
Working of Asp.Net
When a browser requests an HTML file, the server returns the file
When a browser requests an ASP.NET file, IIS passes the request to the ASP.NET engine on
the server
The ASP.NET engine reads the file, line by line, and executes the scripts in the file
Finally, the ASP.NET file is returned to the browser as plain HTML
Advantages of ASP.NET
21 | P a g e
Better language support
Programmable controls
Event-driven programming
XML-based components
User authentication, with accounts and roles
Higher scalability
Increased performance - Compiled code
Easier configuration and deployment
Not fully ASP compatible
Language Support
ASP.NET supports C# (C sharp)
ASP.NET Controls
ASP.NET contains a large set of HTML controls. Almost all HTML elements on a page can be
defined as ASP.NET control objects that can be controlled by scripts.ASP.NET also contains a new
set of object-oriented input controls, like programmable list-boxes and validation controls. A new
data grid control supports sorting, data paging, and everything you can expect from a dataset control.
ASP.NET Components
ASP.NET components are heavily based on XML. Like the new AD Rotator, that uses XML to store
advertisement information and configuration
FFFFFFFF FFFF
22 | P a g e
The first request for an ASP.NET page on the server will compile the ASP.NET code and keep a
cached copy in memory. The result of this is greatly increased performance.
FFFF FFFFFFFFFFFFF
Configuration of ASP.NET is done with plain text files. Configuration files can be uploaded or
changed while the application is running. No need to restart the server. No more metaphase or
registry puzzle.
FFFF FFFFFFFFFF
No more server-restart to deploy or replace compiled code. ASP.NET simply redirects all new
requests to the new code.
FFFFFFFFFFFFF
ASP.NET is not fully compatible with earlier versions of ASP, so most of the old ASP code will
need some changes to run under ASP.NET.
23 | P a g e
FFFF FFF: SQL SERVER 2005
A properly designed database provides you with MS SQL Server Express 2005 to up-to-date,
accurate information. Because a correct design is essential to achieve your goals in working with a
database, investing the time required to learn the principles of good design makes sense. In the end,
you are much more likely to end up with a database that meets your needs and can easily
accommodate change.
When you create a database, you store your data in tables—Subject-based lists of rows and columns.
For instance, you might create a Contacts table to store a list of names, addresses and telephone
numbers, or a products table to store information about products. You should always start the design
of a database by first creating its tables—even before you create any other database objects. Before
you create tables, you should carefully examine your requirements and plan your database to
discover what tables you need.
Becoming familiar with the tables, forms, queries, and other objects in a database can make it easier
to perform a wide variety of tasks, such as entering data into a form, adding or removing tables,
finding and replacing data, and running queries. Ms. SQL server provides several tools that you can
use to familiarize yourself with the structure of a particular database.
Microsoft SQL Server2005 features a number of improvements that make the process of creating a
new database easier.
A properly designed database provides you with SQL server to up-to-date, accurate information.
Because a correct design is essential to achieving your goals in working with a database, investing
the time required to learn the principles of good design makes sense. In the end, you are much more
likely to end up with a database that meets your needs and can easily accommodate change.
Becoming familiar with the tables, forms, queries, and other objects in a database can make it easier
to perform a wide variety of tasks, such as entering data into a form, adding or removing tables,
finding and replacing data, and running queries.
24 | P a g e
Within a SQL Server database file, you can use
1. Tables to store your data.
2. Queries to find and retrieve just the data you want.
3. Forms to view, add, and update data in tables.
4. Reports to analyze or print data in a specific layout.
25 | P a g e
HARDWARE AND SOFTWARE REQUIREMENTS
Hardware Requirements:
TYPE SPECIFICATIONS
Processor Pentium IV or above
Speed 1.8 GHz
RAM 1 GB
MONITOR VGA Color
Hard Disk 80 GB
Input Device Mouse and Keyboard
Software Requirements:
Back End Tools SQL Server 2005
Front End Tools Microsoft Visual Studio 2012
Operating System Window XP
26 | P a g e
FFFFFFF
FFFFFFFFFFF FF
FFF FFFFFFF
Manual filing system is used at the Institute of Management Studies. In this system a manual file is
maintained for the applications received from the candidates. After the deadline for receiving the
applications the security of the applications are done, the applications found incomplete in any form
are rejected, like, percentage less than the required one, supporting documents incomplete, false or
not attached etc.
After the security of the applications a list of the valid applicants is made. Once the applicant
list is ready then a new list is made according to percentage received and this called as the merit list.
Based on this merit list admissions are done.
Modules Description:
Modules:
o Add/Remove User
o Change User ID or Password
Main Interface
Student Module
o Student Admission Form
o Student Employment Detail
o Student Detail
o Student Attendance
Course Module
Marks
Fee
o Fee Collection
27 | P a g e
o Fee Refund
Staff Module
o Staff recruitment
o Staff Attendance
o Salary Payment
Search
Help
Module
28 | P a g e
Project Scope
The main goal of the banking system is to bring convenience to the customers of the bank in order to
meet these objectives; some data and functions should be provided.
The software will consist of the following input:
Administrative information
Customer information
Member information
Reserve information
All of the above data will store in the database in the server.
The software will also consist of the following functions:
Update information
Searching for the database
Collect the suggestion/comments form the customer
Loan Suggestion for the customer
Outputs include:
Detail Information about the Loan
29 | P a g e
Characteristics of the system:
The following are some characteristics of the system
More Systematic
Convenient to Users
Simple Interface
Easy Postage and Retrieval of Data
High Data Security
More Flexible
Efficient Monitoring
Time Efficient
Saves Money
Searchable Database
Certain specific requirements
1. Software Requirements
Platform Used In this project the platform used is a Window XP
30 | P a g e
FFFFFFFFFFFF FF FFFFFF FF
There are many new and exciting features at our fingertips. Some of these features are making
their debut in window xp professional and others have been improved upon since earlier
releases of window. There are new tools you can use to get the most out of your computer
experience, and other technologies that run in the background, making your computer run
more efficiently and reliable.
First, what you can’t see: window XP professional has capability in the behind-the-scenes
running of the computer. Overall security has been improved, making it ever safer for you to
shop and browse on the Internet. You can also communicate with other people on the network
without worrying about compromising your privacy on your personal data files. Performance
is at all-time high, allowing you to use programs and have then run faster than ever. Window
XP professional is dependable and stable, so you can always rely on the performance and
effectiveness on your computer. Best of all, compatibility with other programs is better than
ever.
Now, what you can see: window XP professional has many feature and tools that will make
using your computer easy, effective and entertaining. For example, you can use remote
desktop to access your work computer and its resources from home, and to view and
documents on your computer’s desktop from a co-worker’s computer. With Net meeting you
can have virtual meetings with anyone, anywhere, and you can participate in discussions using
audio, video or chat. Getting help has never been easier: with remote assistance, you just send
e-mail to your favorite computer expert or help desk personnel and they can help you fix a
problem from location.
It helps a person to perform its work with high efficiency and it has some big connectivity
options.
31 | P a g e
Environment Used
Thus project uses the three type of system software developing programming tools; first one is
the visual basic .net by the Microsoft Corporation; second one is the SQL Server, which is a
part of well-known software package called RDBMS and third one is Crystal Reports
developed by Seagate Software system. To present Reports related to process most powerful
tool for reporting Crystal Report is used. In building this project the software’s used are as
follows.
I. Visual basic .Net (as Front End)
II. SQL Server (as Back End)
III. Crystal Reports 7.0(as Reporting Tool)
FFFFF FFF FFFF
Microsoft .Net Framework is a programming infrastructure created by Microsoft for building,
deploying, and running applications and services that use .NET technologies, such as desktop
applications and Web services. The Microsoft .NET Framework is a software framework that can
be installed on computers running Microsoft Windows operating systems. It includes a large library
of coded solutions to common programming problems and a virtual machine that manages
The execution of programs written specifically for the framework.
FFF FFFF FFFFFFFFF.
The .NET Framework is the programming model underlying .NET for developing, deploying, and
running Web services and applications.
Web services are units of code that allow programs written in different programming languages and
on different platforms to communicate and share data through standard Internet protocols such as,
32 | P a g e
XML, SOAP, Web Services Description Language (WSDL), and Universal Description, Discovery,
and Integration (UDDI).
The common language runtime and class libraries are at the center of the .NET Framework. The
common language runtime manages memory, security, and language integration. It also helps
simplify code development and application deployment while improving application reliability. The
bulk of this work is handled transparently, simplifying the work of IT administrators. In addition,
features of the common language runtime—strong type naming, cross-language exception handling,
lifetime management, and dynamic binding—dramatically reduce the amount of code a developer
must write.
Class libraries supply the resources needed to build applications with XML support, networking, and
data-access features. Because the classes are unified, developers can build both Microsoft
Windows®-based and Web-based applications, enhancing their productivity and code reuse in the
process.
FFFFFFFFF FFFF FFF
FFFFFFFFFF
One of the toughest deployment issues developers and IT professionals face involves dynamic-link
libraries (DLLs). It starts when multiple applications attempt to share a common component like a
DLL or a Component Object Model (COM) class. When a new application is installed, the
components for the new application may overwrite components of an existing application, causing
the existing application to function incorrectly or stop functioning completely.
Typically, one application will install a new version of the shared component that is not backward
compatible with the version already on the computer. Although the newly
Introduced application will work fine, existing applications that depended on a previous version of
the shared component may no longer work.
33 | P a g e
Through the use of side-by-side deployment, the .NET Framework solves the problem of
overwriting. Side-by-side deployment allows multiple versions of an assembly to be installed and to
run simultaneously on the same computer. Authors aren't restricted to maintaining backward
compatibility because different applications can use different versions of a shared component. Each
application can request to use a specific version of that assembly. Version information is recorded
through the common language runtime between pieces of an application. At run time, the common
language runtime refers to the recorded information to ensure the proper version of a dependency is
loaded.
By isolating application assemblies, applications always load the components with which they were
built and tested. An assembly can be accessed by only one application; it is not shared by multiple
applications on the same computer. Therefore, it cannot be affected by changes made to the system
by other applications.
.NET enabled applications are self-contained and can be installed easily using XCOPY. This makes
it possible to install desktop applications on client computers using a remote Web server. Actual
deployment involves packaging developer code and distributing the packages to the clients and
servers on which the application will run. The .NET Framework eliminates any dependency on the
registry, which makes installation, removal, and replication much easier. You can deploy many
applications by just copying file sets to disk and running them. To remove or replicate the
applications, you can simply delete the files or copy over them.
FFFFFFFFFFFFFFFF FFF
FFFFFFFFFF
One of the most significant advantages of the .NET Framework is its level of interoperability with
other languages, applications, and systems. At the heart of .NET is the ability to help businesses
integrate and manage their Web-based solutions through Web services, which are quickly becoming
an industry standard.
34 | P a g e
.NET enables modern software applications to communicate through standard Internet protocols
such as XML and SOAP, creating a channel through which internal and remote systems can easily
interact. Applications hosted in-house—in addition to external systems—can be "stitched together,"
allowing businesses to quickly meet their unique business needs through specialized yet economical
solutions.
The common language runtime comes into play by allowing individual components of specific
applications within a company to communicate. Through its standard set of types—self-describing
type information (meta data) and common execution environment—the common language runtime
integrates all programming languages and allows objects created in one language to be read with
equal weight by code written in a different language. For example, a
new scheduling function written in COBOL can be used with an existing human resources
application that was written in Microsoft Visual Basic® .NET.
The advantages of multiple language support are obvious. Not only does it improve productivity by
giving developers the choice to use the programming language that's best suited to the job, it
decreases time to market by increasing code reuse through cross-language inheritance.
FFFFFFFF
Software applications, especially those that are Internet-based, have developed from static channels
designed to alter and orchestrate data into increasingly dynamic exchange systems that form the
foundation of e-business. As the complexity and functionality of modern software applications have
increased, threats to software from both inside and outside organizations have risen.
The managed code architecture of the .NET Framework dramatically reduces the intrinsic risks
associated with both client-side and server-side applications by transparently controlling the
behavior of code. In a private study conducted by Found Stone, Inc., it was determined that a
Microsoft Windows server running the .NET Framework can provide organizations with greater
35 | P a g e
assurance that their applications can resist known security attacks today and in the future. It
eliminates many of the major security risks facing applications today due to flawed code (such as
buffer overruns); and shifts the burden from having to make critical security decisions—such as
whether or not to run a particular application or what resources that application should be able to
access—from end users to developers and administrators.
The comprehensive nature of the .NET Framework security architecture makes .NET both reliable
and trustworthy. Key elements include:
Evidence-based security
Code access security
The verification process
Role-based security
Cryptography
Application domains
These elements help developers and IT administrators control security over applications and
resources on a granular level. Developers get an easy-to-use tool set to implement powerful
authentication, authorization, and cryptographic routines. This helps IT professionals by eliminating
flawed code—one of the biggest threats to application security—so they can focus on critical
security issues involving running other applications and accessing specific resources.
FFFFFF FFFFFFF
One of the biggest advantages of .NET technology for consumers is its ability to connect and support
a wide variety of stationary and mobile devices. IT professionals will appreciate the ease with which
they can facilitate and maintain these connections over time.
Web services play an important role in device support. As mentioned previously, Web services allow
various applications to share information over the Internet, regardless of the operating system or
back-end software that the application is using. They also enable users to interact with a broad range
36 | P a g e
of smart devices through the Web while ensuring that the user—not the application—controls the
interaction.
Powerful client software such as the .NET Compact Framework, Windows CE .NET, and Windows
XP enable a multitude of smart devices to operate and communicate through .NET and Web
services. This collection of software empowers smart devices to access the Internet easily, providing
a positive user experience while giving developers and IT administrators more control over their
information.
.
37 | P a g e
38 | P a g e
SYSTEM DESIGN
FFFFFF FFFFFF
Designing is the most important phase of the software development. It requires a careful planning
and thinking on the part of the system designer. Designing software means to plan how the various
parts of the software are going to achieve the desired goal. It should be done with utmost case
because if the phase contains any error then it will affect the performance of the system; as a result it
may take no processing time, more response time, extra workload etc.
Software design sits at the technical kernel of the software engineering process and is applied
regardless of the software process model that is used. After the software requirements have been
analyzed and specified, software design is first of the following technical activities- Designing,
coding and testing that is required and verifying the software. Each activity transforms the
information in such a manner that ultimately results in validated computer software. This project
Deals with managing the network giving on click information about the connectivity and service
status of the clients.
The system design covers the following:
Reviews the current physical system- its data flow, file content, volumes and frequencies.
Prepare output specifications- that is determining the format, content and the frequency of the
reports, including terminal specifications.
Prepare input specifications- format, content and most of the input functions.
Specifies the implementation plan.
39 | P a g e
Prepares a logical design walkthrough of the information flow, output, input, controls and
implementation plan.
Reviews benefits, costs and system constraints.
LOGICAL DESIGN:
In this analyst writes the detailed specifications of the new system. It includes the major features of
the system and how they are related to one another. It includes input and output specifications, file
and database specifications, processing specifications and requirement data for the new system.
When analyst prepares the logical system design, they specify the user needs at a level of detail that
virtually determines the information flow into and out of the system and the required data resources.
PHYSICAL DESIGN:
This produces the working system by defining the design specifications that tells the programmers
exactly what the candidate system must do. It includes the following steps:
Design the physical system.
1. Specify input/output media.
2. Design the database and specify backup procedures.
3. Design physical information flow through the system and a physical design
walkthrough.
Plan system implementation
1. Determine training procedures.
Devise a test and implementation plan and specify any new hardware/software.
Update benefits, costs and system constraints.
INPUT DESIGN:
40 | P a g e
Input design sis a process of converting user-originated inputs to a computer based format in the
system design phase, the expanded data flow diagram, identifies the logical data flow, data stores,
sources and destinations. After input data are identified, appropriate input media is selected for
processing.
OUTPUT DESIGN:
This is the important and direct source of the information to the user. Efficient, intelligible output
design should improve the system’s relationships with the user and help in decision making. The
output devices to consider depend on factors such as compatibility of the device with the system,
response time requirements, expected print quality and number of the copies needed. The task of
output preparation is critical, requiring skills and ability to align user requirements with the
capabilities of the system in operation.
FORM DESIGN:
A form is a physical carrier of data. It is classified by what it does in the system. While designing a
form, attention is given to proper definition and wording, readability and use, composition and
layout, order of data items and clarity of instructions. A well-designed form with clearly stated
captions should be self-instructing. An organization’s forms must be centrally controlled for efficient
handling.
The system objectives outlined during the feasibility study serve as the basis from which the work of
system design is initiated. Much of the objectives involved at this stage are of technical nature
requiring a certain degree of experience in designing systems, sound knowledge of computers related
technology and thorough understanding of computers available in the market and the various
facilities provided by the vendor. Nevertheless, a system cannot be designed in isolation without the
active involvement of user. The user has a vital role to play at this stage too. As we know that data
collected during feasibility study will be utilized systematically during the system designing .it
41 | P a g e
should, however, be kept in mind that detailed study of existing system is not necessarily over with
the completion of the feasibility study. Depending on the plan of feasibility study, the level of
detailed study will very and the system design stage will also vary in the amount of investigation that
still needs to be done. These investigations generally an urgent activity during the system design as
the designer needs to study minutes detailed in all accepts of the system. But rarely, this
investigation may from a separate stage between feasibility study and computer system design.
Designing a new system is a creative process, which calls for logical as lateral thinking. The logical;
approach involves systematic moves towards the end product keeping in mind the capabilities of
personnel and the equipment at each decision making step. Lateral thought implies encompassing of
ideas beyond the usual function and equipment. This is to ensure that no efforts are being made to fit
previous into new situation.
FFFFFF FFFFFF FFFFFFFFFFFFF
The system design process is not a step-by-step adherence of clear procedures and guidelines.
Though, certain clear procedures and guidelines have emerged in recent days, but still much of
design work depends on knowledge and experience of the designer.
When designer starts working on the system design, he/she will face different type of problems/
many of these will be due to constraints imposed by the user of limitation of the hardware and
software in the market. Sometimes, it is difficult to enumerate the complexity of the problem and
solutions thereof since the variety of likely problems is so great and no solution are exactly similar.
FFFFFF FFFFFFFFFF
The primary objectives of the design phase of course are to deliver the requirements as specified in
the feasibility report. In general following design objectives should be kept in mind:
Practicability: the system must be stable and can be operated by the people with average
intelligence.
Efficiency: this involves accuracy, timeliness and comprehensive- ness of the system output.
Cost: it is desirable to aim for a system with a minimum cost subject to the condition that it
must satisfy all requirements.
42 | P a g e
Flexibility: The system should be modified depending on the changing needs of the user.
Such modification should not entail extensive reconstructing or recreation.
43 | P a g e
CODING
Coding
The primary goal of the coding phase is to translate the given design into source code in a given
programming language, so that code is simple, easy to test, and easy to understand and modify.
Simplicity and clarity are the properties a programmer should strive for.
Good programming is a skill that can only be acquired by practice. However, much can be learned
from the experience of others, and some general rules and guidelines can be laid for the programmer.
Good programming (producing correct and simple programs) is a practice independent of the target
programming language, although some well-structured languages like Pascal, Ada, and Modula
make the programmer's job simpler. In this section, we will discuss some concepts related to coding
in a language-independent manner.
FFFFFFFFF- -
All designs contain hierarchies, as creating a hierarchy is a natural way to manage complexity. Most
design methodologies for software also produce hierarchies. The hierarchy may be of functional
modules, as is the case with the structured design methodology where the hierarchy of modules is
represented by the structure chart. Or the hierarchy may be an object hierarchy as is produced by
object-oriented design methods and frequently represented by object diagrams. The question at
coding time is: given the hierarchy of modules produced by design, in what order should the
modules be, built-starting from the top level or starting from the bottom level?
In a top-down implementation, the implementation starts from the top of the hierarchy and proceeds
to the lower levels. First the main module is implemented, then its subordinates are implemented,
44 | P a g e
and their subordinates, and so on. In a bottom-up implementation, the process is the reverse. The
development starts with implementing the modules at the bottom of the hierarchy and proceeds
through the higher levels until it reaches the top.
Top-down and bottom-up implementation should not be confused with top-down and bottom-up
design. Here, the design is being implemented, and if the design is fairly detailed and complete, its
implementation can proceed in either the top-down or the bottom-up manner, even if the design was
produced in a top-down manner. Which of the two is used mostly affects testing. If there is a
complete design, why is the order in which the modules are built an issue? The main reason is that
we want to incrementally build the system. That is, we want to build the system in parts, even
though the design of the entire system has been done. This is necessitated by the fact that for large
systems it is simply not feasible or desirable to build the whole system and then test it. All large
systems must be built by assembling validated pieces together. The case with software systems is the
same. Parts of the system have to first be built and tested before putting them together to form the
system. Because parts have to be built and tested separately, the issue of top-down versus bottom-up
arises.
The real issue in which order the modules are coded comes in testing. If all the modules are to be
developed and then put together to form the system for testing purposes, as is done for small
systems, it is immaterial which module is coded first. However, when modules have to be tested
separately, top-down and bottom-up lead to top-down and bottom-up approaches to testing. And
these two approaches have different consequences. Essentially, when we precede top-down, for
testing a set of modules at the top of the hierarchy, stubs will have to be written for the lower- level
modules that the set of modules under testing invoke. On the other hand, when we precede bottom-
up, all modules that are lower in the hierarchy have been developed and driver modules are needed
to invoke these modules under testing.
Top-down versus bottom-up is also a pertinent issue when the design is not detailed enough. In such
cases, some of the design decisions have to be made during development. This may be true, for
example, when building a prototype. In such cases, top-down development may be preferable to aid
the design while the implementation is progressing. On the other hand, many complex systems, like
operating systems or networking software systems, are naturally organized as layers. In a layered
architecture, a layer provides some services to the layers above, which use these services to
45 | P a g e
implement the services it provides. For a layered architecture, it is generally best for the
implementation to proceed in a bottom-up manner.
In practice, in large systems, a combination of the two approaches is used during coding. The top
modules of the system generally contain the overall view of the system and may even contain the
user interfaces. Starting with these modules and testing them gives some feedback regarding the
functionality of the system and whether the "look and feel” of the system is OK. For this, it is best if
development proceeds top-down. On the other hand, the bottom-level modules typically form the
"service routines" that provide the basic operations used by higher-level modules. It is therefore
important to make sure that these service modules are working correctly before other modules use
them. This suggests that the development should proceed in a bottom-up manner. As both issues are
important in a large project, it may be best to follow a combination approach for such systems.
46 | P a g e
47 | P a g e
INTERFACE DESIGN
FFFF FFFFF
48 | P a g e
49 | P a g e
50 | P a g e
51 | P a g e
52 | P a g e
53 | P a g e
54 | P a g e
55 | P a g e
56 | P a g e
57 | P a g e
58 | P a g e
59 | P a g e
60 | P a g e
61 | P a g e
62 | P a g e
63 | P a g e
64 | P a g e
TESTING
Testing Phase
The basic goal of the software development process is to produce software that has no errors or very
few errors. In an effort to detect errors soon after they are introduced, each phase ends with
verification activity such as a review.
65 | P a g e
As testing is the last phase before the final software is delivered, it has the enormous
responsibility of detecting any type of error that may in the software. A software typically undergoes
changes even after it has been delivered. And to validate that a change has not affected some old
functionality of software regression testing is performed
No program or system design is perfect; communication between the user and the designer is not
always complete or clear and the time is usually short. The result is error and more error. The main
factor for these errors is mostly communication gap, time constraints and oversight. For this basic
reason testing forms the basis of the success of the system. The testing requires the proper choice of
test data to be provided by the users and then reliability of the output is suspected. The test data may
be artificial or live depending upon the level of the testing being performed on the system. These
levels of testing are given in chronological order here as follows in the diagram:
Levels of Testing:
The basic levels of testing are unit testing, integration testing and system and acceptance testing.
These different levels of testing attempt to detect different types of faults.
UNIT TESTING:
The first kind of testing done at the basic level of the system is the unit testing which checks the
basic functionality at the level of each process defined in the system. It involves the defining the
basic unit test specifications and test data which here is artificial. Each unit of the system is checked
as an independent system with no linkage with any other unit. The defects in the system are logged
and rectified latter on using the technique of debugging.
66 | P a g e
Client Needs
Requirements
System Testing
DesignIntegration Testing
Performance Testing
SYSTEM TESTING:
Once the overall system has been tested and errors rectified at the basic level of the system, the next
level is the testing of the system as a whole. This involves integration of the basic unit of the system
and then testing these integrated units as a whole system. The test data used here is a mix of the
artificial and live data. The system testing involves looking into the security, performance and stress
aspects of the system besides checking the system with respect to the requirements defined by the
user. During this phase, the system is tested as a whole with all modules taken into consideration
with basic aim that the system being developed as a collection of units performing and efficiently.
The system testing started by making the system test specifications, which was on the line of the unit
test specifications but with the system as the basic unit. The system test plan was made and team was
allocated to check the different functionality within the system as a whole. The test database for the
system testing is made and the tables are created in the database. Performance of the system was
67 | P a g e
CodingUnit Testing
measured with respect to the execution of each process with respect to the system as a whole.
Corrective action was taken with respect to what was defined during the analysis and design phase.
Security testing was done for checking the integrity of the system. In this process the system was
tested. Stress testing is done with the voluminous amount of data to check for stress testing.
USER ACCEPTANCE TESTING:
The above two levels of testing are done by the programmer himself without the actual user
intervention though he may take input from the user. Before the start of this phase, the User Manual
of the system should be prepared. User Acceptance testing is done on the system as a whole by the
actual user in a test environment similar to the actual environment. The user is given a basic training
of the system alongside the user manual. The user tests the system with the live data and logs the
errors in a fixed format. These errors are later discussed with the programmer and again tested for
any new or old errors. This process goes on until the user is fully satisfied with the system. Once the
user acceptance testing is over, the user issues the system acceptance letter and the system is ready to
be installed at the actual site.
INTEGRATION TESTING:
Integration testing is a systematic technique for constructing the program structure while conducting
the tests to uncover the errors associated with interfacing. The objective is to take unit tested
modules and build a program structure that has been dictated by design. A top-down integration
approach is used in which the modules were integrated by moving downwards through the control
hierarchy, beginning with the main control module. Modules subordinate to the control module were
incorporated in a depth-first manner. All the visualizations that were done to test the output from the
modules also confirmed that the logical software units have been integrated properly.
68 | P a g e
PERFORMANCE TESTING:
In the test of performance time of inquiry was tested when the designed system was fully loaded
with operating data. Generally the accuracy of the system to efficiently process the transaction
details is judged by the performance test. Performance testing of designed system was being
conducted.
Maintenance
Once the website is launched, it enters the maintenance phase. All systems need maintenance.
Maintenance is required because there are often some residual errors remaining in the system that
must be removed as they are discovered. Maintenance involves understanding the effects of the
change, making the changes to both the code and the documents, testing the new parts and retesting
the old parts that were not changed. Maintenance is mainly of two types:
1. Corrective Maintenance
2. Adaptive Maintenance
7.4.1 Corrective Maintenance:
Almost all software that is developed has residual errors or bugs in them. Many of these surfaces
only after the system have been in operation, sometimes for a long time. These errors once
discovered need to be removed, leading to the software to be changed. This is called Corrective
Maintenance.
7.4.2 Adaptive Maintenance:
Even without bugs, software frequently undergoes change. The software often must be upgraded and
enhanced to include more features and provide more services. This requires modification of the
software. This type of maintenance is known as the Adaptive Maintenance.
69 | P a g e
70 | P a g e
IMPLEMENTATION
Implementation
Implementation is the stage in the project where the theoretical design is turned into the working
system and is giving confidence to the new system for the users i.e. will work efficiently and
effectively. It involves careful planning, investigation of the current system and its constraints on
implementation, design of method to achieve the changeover, an evaluation, of change over
methods. A part from planning major task of preparing the implementation is education of users. The
more complex system is implemented, the more involved will be the system analysis and design
effort required just for implementation. An implementation coordinating committee based on
policies of individual organization has been appointed. The implementation process begins with
preparing a plan for the implementation for the system. According to this plan, the activities are to
be carried out, discussions may regarding the equipment has to be acquired to implement the new
system
Implementation is the final and important phase. The most critical stage is in achieving a successful
new system and in giving the users confidence that the new system will work and be effective. The
system can be implemented only after thorough testing is done and if it found to working according
to the specification. This method also offers the greatest security since the old system can take over
if the errors are found or inability to handle certain types of transaction while using the new system.
71 | P a g e
8.1 There are three types of implementation:
1. Implementation of a computer system to replace a manual system.
2. Implementation of a new computer system to replace an existing system.
3. Implementation of a modified application to replace an existing one, using the same
computer.
Successful implementation may not guarantee improvement in the organization using the new
system, but improper installation will prevent it. It has been observed that even the best system
cannot show good result if the analysts managing the implementation do not attend to every
important detail. This is an area where the systems analysts need to work with utmost care.
8.2 Implementation Tools:
1. Training personnel
2. Conversion Procedures
3. Post-implementation review
72 | P a g e
8.3 Training of Personnel involved with system
Even well designed system can succeed or fail because of the way they are operated and
used. Therefore, the quality of training received by the personal involved with the system in
various capacities helps or hinders and may even prevent the successful implementation of
management information system.
8.4 Conversion Methods
A conversion is the process of changing from the old system to the new one. It must be
properly planned and executed. Four methods are common in use. They are Parallel Systems,
Direct Conversion, Pilot System and Phase In method. Each method should be considered in
the light of the opportunities that it offers and problems that it may create. In general, system
conversion should be accomplished in shortest possible time. Long conversion periods create
problems for all persons involved including both analysts and users.
8.5 Post Implementation Review
After the system is implemented and conversion is complete, a review should be conducted
to determine whether the system is meeting expectations and where improvements are
needed. A post implementation review measures the systems performance against predefined
requirement. It determines how well the system continues to meet the performance
specifications.
73 | P a g e
74 | P a g e
75 | P a g e
CONCLUSION AND SCOPE
CONCLUSION AND FUTURE SCOPE
This chapter provides me an opportunity to do self-introspection of what value I have added to my
knowledge and skill set and to the project.
Conclusion
What value I have added to my knowledge
Domain Experience
Webcom Technologies is an apex institution for the development of balanced urban
growth in the State of Punjab. PUDA is working on various technologies. Also
the individual responsibilities are more. So, I have learnt a lot.
Exposure to entirely different technology
Working on ASP.NET for the first time was a very enriching experience. I had never
worked on this platform earlier. So it added to my list of know how and the computer
languages known to me.
Database Implementation
I had earlier made database but worked on SQL Server for the first time. I learnt many
new things about database creation, concept of stored procedure etc. We learn many
things theoretically as part of our curriculum but here I got a chance to apply my
knowledge practically and enhance it also at the same time.
76 | P a g e
Implementation of Business Logic Layer (BLL)
I have implemented the classes for BLL, which provides the interface between UI Layer
and Data Access Layer. This layer contains all the business logic, i.e. Programming
Methodology to implement the functionality of the system I had always read about N-
Tier architecture but this was again the first time I got to implement 3-Tier logical
architecture. So it was a very new and realistic experience.
Implementation of User Interface Layer (UI Layer)
I have also designed the UI layer that contains the web pages designed in Jsp and Java
Script. Also it contains the Code Behind pages to implement the programming logic.
Hangout.com is very handy tool for connectivity between people. Sharing of knowledge can be done
effectively. Communities regarding company, institute, college, school, any product etc can be
started and information can be exchanged. It can be used as a picture sharing media too as user can
upload pictures and these pictures can be viewed by other friends or people who have permissions.
Files can be uploaded and hence can be transferred easily within second.
As this is Social Networking site so its application is not very specific. Applications vary with its
type of use by community of people who are using it. Since conclusions regarding the project are not
so specific but only the main conclusion drawn from the project is that it can be a better social
networking site by the marketing .considered as a next web application corresponding to another
sites for social network among the society people
77 | P a g e
Future Scope
Completion of the development process will result in a software package that will provide user-
friendly environment, which is very easy to work with, even for people with very little knowledge of
computer.
Management of various tasks is incorporated in the package and will deliver the required
information in a very easy to use and easy to access manner.
This package will provide accuracy, efficiency, speed and easiness to the end user. Since the system
is verified with valid as well as invalid data and is run with an insight into the necessary
modifications that may require in the future, it can be maintained successfully without much
78 | P a g e
79 | P a g e