1 INTRODUCTION
1.1 INTRANET MAILING SYSTEM
The "Intra "Intranet net Mailin Mailing g System System"" has been develop developed ed out of a need need for communica communication tion between between the Faculty(s) and the students.The " Intranet Intranet Mailing Mailing System" System" provides provides a means by which students students can place their queries,repl queries,reply y to each others queries, queries, send each others mails and basically keep in touch across the " ", network. This application has been designed keeping in mind two types of members(Students and Faculty),before the members can start sending mails they have to register with at this website and as soon as they register they will be provided with a unique Email address, using this Email ID the member can login to the mailing service from any computer on the network and check his mailbox.
Core Features: •
Intranet email facility among students and faculty members
•
Works as standalone system without requiring any external resources from the Internet
•
Also incorporates Online Feedback facility about the software
•
Personified Login and Mailing Mailing pages for different categories of members
1.2 SYSTEM STUDY 1.2.1 PROPOSED SYSTEM:
The proposed system “Intranet Mailing System” includes•
Registration of Students, Instructor.
•
Mailing Facility
•
Provide Feedback Facility
•
Administrator Authorization
1
1.2.2 ADVANTAGES OF PROPOSED SYSTEM: The proposed system has following
advantages•
User can interact with any one on the network through mailing system.
•
Proposed system is Intranet enabled.
•
Only Administrator can check number of logins, total mails, feedback
1.3 SYSTEM ANALYSIS
System analysis analysis is an in –depth of the end user information information needs that produces functional requirements that are used as the basic for the design of the new system. System analysis traditionally involves detailed study of:•
The information needs of the organization and end users like you.
•
The activities, resources, and outputs of the present system in a familiar manner.
•
The system capabilities required to meet your information
Need, and those those of others others staff staff member member of the the organization. organization.
There are following steps in the system analysis:•
Organization Analysis.
•
Analysis of the present system.
•
Functional requirements analysis.
1.4 Software Requirements:
Hardware
Pentium IV – 2.0, 128 MB RAM, 40 GB HDD
Operating System
Windows XP
Software Environment
MS.NET (Front End) MS-SQL Server (Back End)
Documentation
Microsoft Word 2000
2
1.4.1 FEASIBILITY STUDY
Feasibil Feasibility ity is the determ determinat ination ion whethe whetherr or not a projec projectt is worth worth doing. doing. The process process followed in making this determination is called feasibility study. Since Since the the feas feasib ibil ilit ity y study study may may lead lead to comm commit itme ment nt of larg largee reso resour urces ces,, it becom becomes es necessa necessary ry that it should should be conducte conducted d compet competent ently ly and that no fundame fundamental ntal errors errors of judgment are made. made. Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. Three important tests of feasibility are described below:-
1.4.1.1. Technical feasibility: This is concerned with specifying equipment and software
that will successfully satisfy the user requirement. During the analysis of the technical feasibility of the system, it is considered that •
It should produce outputs in a given time.
•
It should give quick response under certain condition. And,
•
The hardware should be able to process certain volume of transactions at faster speed.Since the project comes under the category of database management system, so here MS SQL Server Server is used used as database. database. The reason reason for choosing choosing MS SQL Server that it is easy to use. C# .Net is used as Front-end for MS SQL Server With the above configuration of hardware system and aforesaid software, the system will will be entirel entirely y technica technically lly feasib feasible. le. One more import important ant point point has also been been considered that if the BIIPL proposes any changes in it’s working conditions, the system should also react to that and it can easily be upgraded
. 1.4.1.2. Operational Feasibility: The project has been designed considering all future
scopes that can come into the consideration consideration in the near future and also considering considering that the organization can make some changes in its working environment or operational structure, or it can add some new skill that can be essential in near future. At this level the project is almost operationally feasible because the system has been 3
designed so efficiently that a person having little knowledge of computers can handle the system very well. The user may not know every little part of the system but the project should support him in the way that he can easily understand information’s and may respond according to that.
Software requirement specification:
A complete specification of the software requirement is essential to the success of Software development efforts .No matter how will designed and well coded, a poorly specified program program will disappoint disappoint the user and bring grief grief to the developers the requirement requirement analysis analysis task is a process of discovery and refinement .The software scope, initially establish is refined in details alternative solutions are analyzed to various software elements. Software Requirement Specification is conducted with the following objectives in mind: •
Identify the customer’s need.
•
Evaluate the system concept for feasibility.
•
Perform economic and technical analysis.
•
Allocate functions to hardware, software, people, database, and Other system elements.
•
Establish cost and schedule constraints.
•
Create a system definition that forms the foundation for all Subsequent work.
Software Requirement Specifications (SRS) will facilitate the developer & educate the user on all aspects of the computerized system. Every function, feature and constraint that is required for the system is documented here. This document attempts to give an overall functional and performance requirements of this System.
4
1. Funct Function ional al Requ Requir irem ement entss
1.1.1.
Registration:
Purpose
To Register student and instructor.
Inputs
User’s click on “SUBMIT” button.
Processing
Outputs
Stor Storee all all the val validat idateed info inform rmat atio ion n in to the database. Message indicates that you are registered properly.
1.1. .1.2. Login:
Purpose Inputs Processing Outputs
To
logi login n
authe uthent ntic icat ated ed
admi admin, n,
stud studeents nts
and and
instructor. Valid username and password Firs Firstt do the clie client nt side side val validat idatio ion n and and then then authenticate the user after verifying from database. Student , instructor or admin redirect to mail page
1.1. .1.3. Inbox: Purpose
Interface to the user to check his/her email
Inputs
No input input Required. Required. It figures out the email selected by the user to be
Processing read and queries the database for the information
corresponding to the email message selected. Outputs
Provides a message in the standardized email format
1.1.4 .1.4.. Outbox: ox: Purpose
To check the sent details 5
Inputs Processing Outputs
No Input It inter interact actss with with databa database se and and retr retriev ieves es the the sent sent emails by the user, if any Display of sent email information in tabular format
1.1. 1.1.5. 5. Chan Change ge Pas Passw swor ord: d: Purpose
To change password of student or instructor
Inputs
Old and new password
Processing Outputs
Veri Verify fy the the old old pass passwo word rd from from data databa base se and and if verified then update new one. New password password is is confirmed. confirmed.
6
Data Flow Diagram:
As information moves through the software, it is modified by a series of transformation .A Data Flow Diagram (DFD) is a graphical technique that depicts information flow and transfers that are applied as data moves from input to output. The DFD is also known as Data flow graph or a bubble chart. The data flow diagram may be used to represent a system or software at any level of abstraction. In fact, DFD’s may be partitioned partitioned into into levels levels that represe represent nt increasing increasing informati information on and functional functional detail. detail. The basic notation to create a DFD is: A rectangle is used to represent an external entity, that is, a system element (e.g. hardware, person and another another program) program) or or another another Syste System m that that prod produce ucess infor informa mati tion on for for trans transfo form rmat atio ion n by the the soft softwa ware re or rece receive ivess information produced by the software. A circle represents a process or transform that is applied to data (or control) and changes it in some way. An arrow represents one or more data items. An open rectangle represents data store –stored information that is used by the software, i.e. temporary repository of data. The simplicity simplicity of DFD notation is one reason why structured structured analysis analysis techniques are most widely widely used .The data flow diagram for the current system is as given in the figure on the next page:
7
CONTEXT DFD:
Instructors
Student
Intranet Mailing System
Administrator
DFD Level-1
8
DFD Level-2
9
ER-DIAGRAM 1:
S Id
S SNo
SNam e
Mess
R RId
M Msg Collector
a age
R D Date
R
R Subje
Flag
Name N
ct c
ER-DIAGRAM 2:
S Id S SNo
S SName
Messa
R RId
M Msg Collector1
g ge
R Date D
R Subje
Flag
R N Name
c ct
ER-DIAGRAM 3:
10
FNa
Phon
A Age
m me
I Id
e
A
S Student_Personal_Info
B Emai LNa
l
Roll
m me
N No
Addr
C
e ess
ER-DIAGRAM 4:
Y Year B Board
College C
A A
Student SSCEDU E Universit P Percent
y
11
ER-DIAGRAM 5:
Year Y College C
B B
Board B
Student HSCEDU E
Universi t ty
P Percent
ER-DIAGRAM 6:
Year Y
B Board
College C
C C
Student GradE EDU
Universit
Percent P Id I
P Password
y
ER-DIAGRAM 7:
L Log_In
12
User Name U
ER-DIAGRAM 8:
S Serial No
Stud N Name
S Subject
F analysis Feedback Object oriented D Date
M Message
Objec Objectt orie oriente nted d anal analysi ysiss is conce concerne rned d with with deve develop loping ing soft softwa ware re engine engineer ering ing and specification that expressed as a systems object model as opposed to traditional data or functional views of a system .OOA can yield following benefits maintainability through simplified mapping to the real world, which provides less analysis effort, less complexity in system design and easier verification by the user reusability of the analysis artifacts which which sales sales time time and costs; costs; and dependi depending ng on the analysi analysiss model model and progra programm mming ing language, productivity games through direct mapping to features of data modeling .
13
Data Data Mode Modeli ling ng:: Mode Modeli ling ng is is a cen centr tral al par partt of all all acti activi viti ties es that that ads ads up up to to depl deploy oyme ment nt of good software we build models to communicate the desire structure and behavior of a system we built the models models to visualize visualize control control system system architecture. architecture. We built built models models to better understand understand the system we are building, building, after exposing exposing opportunities opportunities for simplification and reuse we build models to manage risks. Modeling is proven and well accepted engineering technique. A model is a simplification of reality. Unified Modeling Language: Visualizing, specifying, constructing and documenting object oriented system is exactly the purpose purpose of UML.UML UML.UML is standard standard language for writing writing software software blue prints. prints. It is very expressive language, easy to understand and easy to use, addressing all the views needed to develop and then deploy software systems. Object oriented design:
14
Object Oriented Design is design strategy where system designers think in terms of ‘things’ (objects) instead of operations of functions. The executing system is map of interacting object objectss that that maint maintai ain n their their own own local local state state and and provi provides des oper operat atio ion n on the the state state inform informatio ation. n. An Object Object Oriente Oriented d Design Design proces processs involve involvess designi designing ng objects objects and relationships between these classes. When design is realized as an executing program, the required objects are created dynamically using class definitions. An important advantage of an object oriented approach is that simplifies the problem of making changes to design. Changing interval details of objectives unlikely to affect any other system objects further more, because objects are usually coupled, usually straig straight ht forwar forwards ds to introdu introduce ce new objects out signifi significant cant effects effects on the rest rest of systems. The various UML diagrams for the various sub system involved in our website are given below b elow.. Class Diagram: Class diagram are the back bone of object oriented modeling. Class diagram shows static descriptive view of system diagrams visualize, specify, construct, document, structure of system that is definition. These diagrams are built with structural things like classes, interaction, interaction, collaboration collaboration relationships relationships between them thus class diagram diagram represent represent design view of a system. Classes Classes repres represent ent an abstract abstraction ion of entitie entitiess common common and characte characterist ristics ics.. Associa Associatio tions ns represent the relationships between classes. Definition: A class diagram is graphical notation that shows set of classes, interfaces, collaboration and their relationship graphically. Graphically it is a collection of vertices and arcs, classes and interfaces are represented as vertices on relation ships as arcs connecting classes together. Some times these arcs are represented with extension symbols and different form to represent different types of relationships. Advantages of class diagrams:
It designs static view of a system. This view provides functions of systems, services of system to end users.
15
It models vocabulary of system. This means defining abstraction from information which is a part of a system.
It models simple collaboration. Collaboration is society of classes, interfaces that connect together with common specifics operation implementation.
Class Class diagra diagrams ms are useful useful to model model logical logical database database schema schema based based on object object orientation that is to design data base on object orientation called object oriented database.
16
Components Diagram: Component diagram models the instances of things continue in classes’ diagrams. That is used to model the instances of classes and interfaces, relationships defined, modeled in class diagram. A component diagram that shows set of components and their relationships at a point in time. time. A compone component nt diagram diagram is collecti collection on of vertice verticess and arcs arcs between between vertices vertices here here component are acted as vertices and arcs represent relationships between vertices. A component diagram commonly contains
Objects
Links
Component diagram also contains packages or subsystems. Thus a component diagram is essential instance of class diagram. Component are instances of classes found in class diagram where as lines are relationships between between objectives objectives at run time. time.
17
Use Case Diagrams: Use case diagram identify the functionality provides by the system (use cases), identifies users who interact with the system (actor) and provides provides association between users and use cases. This model behavior of a system with respect to users it shows the dynamic aspects of the system then user interact with the system. A use case can have all possible interactions of users with use case graphically. Thus use case diagram models use case view of a system. Definition: A use case diagram is set of use cases, actors and relation ships between actors use cases A use case diagram contains:
Use cases
Actors
Association relationship between actors, use cases
Generalization between actors
Include , extent, generalization relationships
Common uses of use case diagram:
Provides high level view of a system with respect to user
To model context of a system
Determine human system interaction
The basic components in use case diagram are:
Use case
Actor
Association
Use case: It is functionality provided by system to user. Example: lodges a complaint, provides user id and password Use case is represented graphically as ellipse with name inside it 18
Actor: An actor is a user of a system of data base in a system it is represented with stick figure Association: Association links actors to use case explain in what way and how actor interacts
Sequence diagram: A sequence diagram is an interaction diagram that emphasizes emphasizes the time ordering of messages. A sequence diagram shows a set of objects and the messages sent and received by those objects. This commonly contains •
Objects 19
•
Links
Messages System level sequence diagram
•
Login
20
View details sequence diagram
Articles:
21
Collaboration Diagrams
22
23
.
24
VERIFICATION & VALIDATION Validation Specification: The terms verification and validation are used interchangeably, verification is a processes processes of determining determining whether whether are not the products products of given phase of software software develop development ment fulfil fulfilll the specif specificat ication ion establ establishe ished d during during the previou previouss phase. phase. The activities activities include providing, providing, testing and previous. previous. Validation is a process process of evaluating evaluating the software the software at end of software development development process to find out how well the software satisfies requirement specification. The development of software starts with requirement document and is there fore impo import rtant ant that that requi require reme ment nt spec specif ifica icati tion on conta contain in no erro errorr and spec specif ifie iess clie client’ nt’ss requirements correctly. The validation process of evaluating deployment system at an end is must must,, to ensur ensuree that that it meet meetss all all neces necessa sary ry requi require reme ment nt spec specif ifica icati tions ons.. Requirement verification also checks the factors as complete ness, consistency and testability of the requirements. The major major verific verificati ation on and validat validation ion activit activities ies for softwa software re developm development ent are transactions, queries and reports. Trans Transact action ion and and querie queriess are are perf perfor orme med d in orde orderr to check check variou variouss input inputss and expected outputs. These outputs are checked against the existing document to see whether they are matching or not. Inspections and reviews are performed in order to be careful with calculations being made. The primary purpose of review was to detect the defects at different stages during the project. The review processes is generally done by group of people including author author of product product,, depart departmen mentt head and a person person from each each phase phase preced preceding ing and succeeding the current phase under review. The review material usually includes specification, system design, detail, design code and test plan. Proper execution of reviews is critical to successes of project. According to pressman “validation criteria” is probably the most important, and, ironically, the most often neglected section of SRS. How do we recognize successful impl implem ement entat ation ion?? What What loss losses es of tests tests must must be condu conduct cted ed to valida validate te funct function ional al performance performance and constrains? constrains? Specification Specification of validation validation criteria criteria acts as an implicit implicit review of all other requirement. Reasonable expectations are defined in SRS under this section section and user user visible visible attribu attributes tes of softwa software re are also also defined defined here. here. Informa Informatio tion n contained in this section forms the basis for a validation testing approach. TESTING Software testing is a critical element of software quality assurance and represents the ultimate role of specification, design and code generation. 25
Once the source code has been generated, software must be tested to uncover as many errors as possible before delivery to consumer. We have to design a series of test cases that have high likelihood of finding errors. The strategies provide systematic guidance of designing tests that
Exercise the internal logic of software components and
Exer Exerci cise se the the inpu inputt and outpu outputt doma domains ins of prog progra ram m funct functio ion, n, behav behavio iors rs and performance. performance. Testing principles:
All tests should be traceable to customer requirements.
Test should be planned long before testing begins.
The highly error prone components of the software products should be recognize and thoroughly exercise.
The testing should start from small components to large components.
For effective testing, team should be a third party rather than developer and client
The physical system specifications are turned over to programmers at the part of the implementation space. It is last phase of SDLC. It is most expensive and time consuming phase of entire life cycle. During implementation, you turn system specification into a working system i.e., tested and then put into use. Implementation includes coding, testing and instillation. Hence we mainly concentrate on the various types of tests and preparation of user manual. FUNCTION ORIENTED TESTING: This can be broadly classified into two categories based on the area in which tests are conducted. They are
White box testing
Black box testing
White Box Testing: White box testing, some time called glass box testing is a test case design method that uses the control structure procedural procedural design to drive the test test cases. cases. As specif specified ied design design space space the inputs inputs are consider considered, ed, actual actual processing processing that that goes on with with in the the system system and final final output. output. The test test was was exte extensi nsive vely ly condu conducte cted d and check checked ed again against st the the specification given in the design phase module.
Black Box Testing: Black box testing focuses on the functional requirements of the software. It enabl enables es the the softw softwar aree engine engineer er to deri derive ve the sets sets of input input condi conditi tion on for a program. program. Black box testing is not an alternate to white box testing techniques. Here 26
we no longer consider the independent working of each module separately. Rather we aggregate them together to test if they perform the required goals and objectives has specified in study phase. For testing, we had to resort both the sample and real data. In all area the real data was made available to us by our effort in collection them from the engineering department of the hotel.
Unit Testing: Here the entire software system is tested. The reference document for the processes is requirement document and the goal if system meets its requirements.
Boundary Condition Test: Boundary conditions as in the case of generating sequences ware tested he ensure that module operates properly at boundaries establish to limit of restricts processing.
Acceptance Test: This This is norma normall lly y perf perfor orme med d with with real realist istic ic with with data data of the the clie clients nts to demonstrate that the software is working satisfactory. Testing here focuses on the external behavior of the system.
27
DAT DATABASE DESIGN: Data bases are normally implemented by using package called database management system system (DBMS).Each (DBMS).Each particular DBMS has some what unique characteristics, characteristics, and so such, general technique for the database are limited. One of the most useful methods of analyzing the data required by the system for the data dictionary has develop developed ed from from resear research ch into into relatio relational nal databas database, e, partic particular ularly ly the work work of E.F Codd. This method of analyzing data is called “Normalization”. UN normalized data are converted into normalize normalize data by three stages. Each stage has procedure to follow. NORMALIZA NORMALIZATION TION:: The first stage of normalization is to reduce the data and to its first normal form, by removing repeating terms showing them as separate records but including in them the key fields of original record. The next stage of reduction to the second normal form is to check that the record, which one is first normal form, all the items in each record are entirely dependent on the key of the record. If a data is not dependent on the key of record, but on other data item, then it is removed with its key to form another record. This is done until each record contains data items, which are entirely dependent on the key of their record. The final stage of analysis, the reduction of third normal form involves examining each record which one is in second form to see whether any items are mutually dependent. dependent. If there are any item there are removed to a separate separate record leaving one of items behind in the original record and using as the key in the newly created record. RELATIONAL DATABASE MANAGEMENT: A relational database management system only its relational capabilities to manage the information store in its databases . INFORMATION REPRESENTATION: All information stored in a relational is represented only by data items values values,, which which are stored stored in tables tables that that makeup makeup the databa database. se. Associa Associatio tions ns between data items are not logically represented in any other way, such as a use of pointers from one table to another. LOGI LOGICA CAL L ACC ACCES ESSI SIBI BILI LITY TY:: Ever Every y dat dataa ite item m val value ue stor stored ed in rela relati tion onal al data data base base is accessible by stating nature of table it is stored name of column under which it is stored and value of primary key that defines the row in which it is stored.
28
REPRESENTATION OF NULL VALUES: The database management system has a constitute method of representing null values. For example, null values for numeric data must be distinct from zero or any other numeric and for character data it must be different from string of blanks or any other character value. CATALOGUE FACILITIES: The logical description of relation database is represented in the same manner or ordinary data. This is done so that facilities of relational database management system itself can be used to maintain database description. DATA LANGUAGE: The relational database management system may support many types of languages for for descr describi ibing ng and acce access ssing ing databa database. se. Howe However ver,, ther theree must must be at least least one language that uses ordinary character strings to support the definitions if data, the definition definition of views, manipulation manipulation of data, constrains on data integrity, information information concerning authorization and the boundaries for recovery of units. VIEW UPDATABILITY: Any view that can be defined combination of basic tables that are theo theoret retic ical ally ly upda updata tabl ble, e, thes these e capit capital als s of bein being g upda update ted d by the the rela relati tiona onall database management system. INSERT, UPDATE & DELETE: Any operand that describes the result of single retrieval operation is capable of being applied applied an an insert, insert, update or delete operati operation on as well. well. PHYSICAL DATA INDEPENDENCE: Changes made to physical storage representation or access methods do not require changes to be made to application programmers. LOGICAL DATA INDEPENDENCE: Changes made to tables that do not modify any data stored in that table, do not require changes to be made to application programmers . INTEGRITY CONSTRAINTS: Constraints that applied to integrity and referential integrity are specifiable by the data language implemented by the database management system and not by the statements coded into the application programs .
29
DATABASE DISTRIBUTION: The data language implemented by the relation management system supports the ability to distribute database without requiring changes to be made to application programmer programmerss this facility facility must be provided provided in the data language, language, whether whether are not the database management system itself supports distributed databases. NON SUB SUB VERSION: VERSION: If the rela relati tiona onall databa database se manag managem ement ent syst system em supp suppor orts ts facil facilit ities ies that that allo allow w application programmers to operate on that table or a row at a time, an application programmer programmer using this type access is prevented prevented from by passing passing entity integrity or referential integrity constraints that are defined for the database. LOGICAL SCHEMA: A Logical Logical Schema Schema is a data model model of a specifi specificc proble problem m domain domain that is in terms of a particular particular data management management technology. technology. Without Without being specific specific to a particular particular database management product, it is in terms of either (for example, in 2007) relational tables and columns, object-oriented classes, or XML tags. This is as opposed to a conceptual data model, which describes the semantics of an organization without reference to technology, or a physical data base model, which describes the particular physical mechanisms used to capture data in a storage medium. CONCEPTUAL SCHEMA: A conceptual schema or conceptual data model is a map of concepts and their relationships. This describes the semantics of an organization and represents a series of assertions about its nature. Specifically, it describes the things of significance to an organization (entity classes), about which it is inclined to collect information, and characteristics of (attributes) and associations between pairs of those things of significance (relationships). Because it represents the semantics of an organization, and not a database design, it may exist on various levels of abstraction. The original ANSI four-schema architecture began with the set of external schemas that each represents one person's view of the world around him or her. These are consolidated into a single conceptual schema that is the superset of all of those external views. A data model can be as concrete as each person's perspective, but this tends to make it inflexible. inflexible. If that person's world changes, changes, the model must change. Concept Conceptual ual data models models take a more more abstra abstract ct perspe perspecti ctive, ve, identif identifying ying the fundame fundamental ntal things, of which the things an individual deals with are but examples. The model does allow for what is called inheritance in object oriented terms. The set of instances of an entity class may be subdivided into entity classes in their own right. Thus, each instance of a sub-type entity class is also an instance of the entity class's super-type.
30
Each instance of the super-type entity class then is also an instance of one of the sub-type entity classes. Super-type/sub-type relationships may be exclusive or not. A methodology may require that each instance of a super-type may only be an instance of one of one sub-type. Similarly, a supertype/sub-type relationship may be exhaustive or not. It is exhaustive if the methodology requires that each instance of a super-type must be an instance of a sub-type.
31
TECHNOLOGY USED
MS.NET(FRONT- END):
The .NET .NET Fram Framew ewor ork k is a devel developm opment ent and execut execution ion envir environm onmen entt that that allow allowss diffe differe rent nt programming programming languages languages & libraries libraries to work together seamlessly seamlessly to create Windows-base Windows-based d applications that are easier to build, manage, deploy, and integrate with other networked systems. The .NET Framework consists of: •
The
Common
Language
Runtime
(CLR)
A language-neutral development & execution environment that provides services to help "manage" application execution •
The
Framework
Class
Libraries
(FCL)
A consistent, object-oriented library of prepackaged functionality
32
Busines nesss today today dema demands nds a diffe differe rent nt kind kind of data data MS-SQ MS-SQL L Ser Server ver : (Bac (Back k end) end) Busi management solution. Performance, scalability, and reliability are essential, but businesses now expect more from their key IT investments.
SQL Server 2000 exceeds dependability requirements and provides innovative capabilities that that incre increase ase empl employe oyeee effe effect ctive ivenes ness, s, inte integr grat atee heter heteroge ogeneo neous us IT ecosy ecosyst stem ems, s, and maximize capital and operating budgets. SQL Server 2000 provides the enterprise data manag managem ement ent plat platfor form m your your organi organiza zati tion on needs needs to adap adaptt quickl quickly y in a fastfast-cha changi nging ng environment. With the lowest implementation and maintenance costs in the industry, SQL Server 2000 delivers delivers rapid return on your data management management investment. SQL Server 2000 2 000 supports supports the rapid development of enterprise-class business applications that can give your company a critical competitive advantage. Bench Benchma mark rked ed for for scal scalabi abili lity ty,, spee speed, d, and perf perfor orma mance nce,, SQL SQL Serve Serverr 2000 2000 is a fully fully enterprise-class database product, providing core support for Extensible Markup Language (XML) and Internet queries. Easy-to-Use Business Intelligence (BI) Tools
Through Through rich rich data data analysis analysis and data data mining mining capabi capabilit lities ies that integrate integrate with with famili familiar ar applications such as Microsoft Office, SQL Server 2000 enables you to provide all of your employees with critical, timely business information tailored to their specific information needs. Every copy of SQL Server 2000 ships with a suite of BI services. Self-Tuning and Management Capabilities
Revolut Revolutiona ionary ry self-tu self-tuning ning and dynamic dynamic self-co self-config nfiguri uring ng features features optimi optimize ze databas databasee performance, performance, while management management tools automate automate standard standard activities. activities. Graphical Graphical tools and wizards simplify setup, database design, and performance monitoring, allowing database administrators to focus on meeting strategic business needs.
33
Testing:
Software Testing is the process of executing a program or system with the intent of finding errors or it involves any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. Software testing is a process used to identify the correctness, completeness and quality of developed computer software.
Testing Framework:
To begin with, let us look at the traditional Software Development life cycle. The figure below depicts depicts the the same. same.
Requirements
Requirements
Design
Design
Code
Code
Test
Maintenance
T e s t
Maintenance
34
Fig A
Fig B
In the above diagram (Fig A), the Testing phase comes after the Coding is complete and before the the product product is launched launched and goes goes into maintenance. maintenance. But, the recommended test process involves testing in every phase of the life cycle (Fig B). During the requirements phase, the emphasis is upon validation to determine that the defined requirements meet the needs of the organization. During the design and program phases, phases, the emphasis emphasis is on verification verification to ensure that the design and programs programs accomplish accomplish the defined defined requireme requirements. nts. During During the test test and install installati ation on phases phases,, the emphasi emphasiss is on inspect inspection ion to determ determine ine that the implem implement ented ed system system meets meets the system system specifi specificat cation. ion. During the maintenance phases, the system will be retested to determine that the changes work and that the unchanged portion continues to work.
Testing Techniques:
In this project we have used the following testing techniques
1. Unit testing:
Goal of Unit testing is to uncover defects using formal techniques like Boundary Value Analysis (BVA), Equivalence Partitioning, and Error Guessing. Defects and deviations in Date formats, Special requirements in input conditions (for example Text box where only numeric or alphabets should be entered), selection based on Combo Box’s, List Box’s, Option buttons, Check Box’s would be identified during the Unit Testing phase. Following validation checks are performed during the unit testing a) Validation for Numeric Entries: - This validation checks whether an entry in the text box is numeric or not. If not, a suitable message is flashed to user. b) Validation for Mandatory Entries: - This validation checks whether mandatory entries are filled or not. If not, a suitable message is flashed to user.
35
c) Validation For Unauthorized Entry:- This validation checks for validity of user for making entries or modification .If user is not authorized than such a user is prevented prevented from executing the software. software.
2. Integration testing:
Integration testing is a systematic technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested components and build a program structure that has been dictated by design. In these testing forms means for relevant schemes schemes that have already been tested during the unit testing are integrated into one module namely online monitoring of land reforms schemes, this system is then tested thoroughly for the errors.
3. System testing:
The system was tested with the test data and it was put to its all limits so that various exceptions and errors could be detected. It was tested for these exceptions •
Validation Validation checks for numeric entries, for date type data, and for blank text entries are working properly or not. So that wrong data is not added to database.
•
Data addition, modification modification and deletion should result in change of values in to the database.
•
Data can be retrieved properly from the database on making right query.
•
Database transaction carried out properly or not.
•
Recovery of data in failure conditions.
36
IMPLEMENTATION:
Implementation Platform:
At server side
Hardware requirement Pentium-III processor or above 128 MB RAM 20 GB Hard Disk Software requirement Microsoft windows 2000 SQL Server 2000 IIS 6.0
At Client site
Hardware requirement Pentium processor or above 64 MB RAM Microsoft Internet explorer or any Internet browser
37
Conclusion:
The application has been loaded on the server and can be accessed
I conclude my project by discussing the future extensions of this project. In the future I would like to add some features extra features in this project, which are as follows: 1. This applicat application ion can be made made highly secured secured by adopting adopting several several securit security y strategies strategies and techniques. 2. Flexibi Flexibilit lity y can be inbuilt inbuilt in the project project,, so as to include include as many many modules modules as are required, e.g. we can include attachment in our mailing system and an address book. 3. The The secur securit ity y of the data entry entry forms forms depe depends nds on the user user name and passw passwor ord d combinations, which authenticates the users. More sophisticated methodologies like digital signature can be employed to restrict access and minimize the threat to the data.
BIBLIOGRAPHY
1.
“ASP .Net” by Wrox Publications.
38
2.
Wrox Publications. Publications. “C#.Net” by Wrox
3.
“ ADO.Net” by Wrox Publications.
4.
Rajib Mall. Mall. “Software Engineering” Engineering” by Rajib
5.
“DataBase Concepts” by Korth.
6.
Websites:
www.msdn.com www.microsoft.com www.google.com www.biipl.com
39
