Sunbeam Institute of Information Technology: A Project On "Online Book Store"

A PROJECT ON
“Online Book Store”
SUNBEAM INSTITUTE OF INFORMATION TECHNOLOGY

Plot No. R/2, Market Yard Road,
Behind Hotel Fulora, Gultekdi, Pune - 411037
Maharashtra
020 2427 2383
1
TABLE OF CONTENTS
1. Introduction of Project
2. Product Overview and Summary
2.1 Purpose
2.2 Scope
(a) Definitions
(b) Acronyms
(c) Abbreviations
2.3 References
2.4 Overview
3. Overall Description:
4. Requirements
4.1 Functional Requirements

4.1.1 On-line Alumni Record Entry
4.1.2 Administration Tasks
4.1.3 Alumni’s Task
4.1.4 Counselor’s Task
4.1.5 Placement coordinator’s Task
4.2 Non-Functional Requirements

4.2.1 Interface
Go to Appendix B for user interfaces
4.2.2 Performance
4.2.3 Constraint
4.2.4 Other Requirements
5. Design
5.1 Database Design
6. Coding Standards Implemented
7. Test Report
8. Project Management Related Statistics
2
1. Introduction of Project:
The main objective of the project is to create an online book store that allows users to
purchase a book based on title, author and subject. The selected books are displayed in a
tabular format and the user can order their books online through credit card payment. The
Administrator will have additional functionalities when compared to the common user.
Online Book store is an online web application where the customer can purchase books
online, through a web browser. The customers can select a book; later can add to the
shopping cart and finally purchase using credit card transaction. The
users can login using his account details or new customers can set up an account very
quickly. The books are divided into many categories based on subject like Fiction, Cooking,
Adventure, etc. anonymous
The web application will provide the basic functionalities to the users, i.e. selecting the
book, putting the same in the cart and purchasing it in the end. Rather than this the
users will also get the facility to browse the complete site either being a guest or as a
registered customer. But in order to purchase users have to become a registered
customer.
The Administrator is responsible and authorized to fill up the data into the database as
well as Update the data accordingly. The data filled by person during registration will be
entered into database by the utility provided. Our software is easy to use for both
beginners and advanced users. It features a familiar and well thought-out, an attractive
user interface.
The software Library Management System has four main modules.
 Insertion to Database Module – User friendly input screen

 Extracting from Database module – Attractive Output Screen
 Report Generation module – Sold book list & Available book list
3
2. Product Overview and Summary
2.1 Purpose:
 To shop while being in the comfort of your own home, without having to step out
of the door.
 Sell at lower rate due to less over head.
 Provide home delivery free of cost.
 No wait to see the products if someone else are taking that.
2.2 Scope:
The Online Book Store is an easy to maintain, ready to run, scalable, affordable and
reliable cost saving tool from Software Associates suited for small, medium, and large
shopping complex and shopping malls.
The proposed system can be used even by the naïve users and it does not require any
educational level, experience, and technical expertise in computer field but it will be of
good use if the user has the good knowledge of how to operate a computer.
2.3 References: www.oxfordbookstore.com, http://google.com
4
3. Overall Description:
3.1 Product Perspective:
The Product is a web-based product, which will be used by multiple users i.e. the
administrator, registered user and guest. Administrator will be provided with the
Interface, with the help of which administrator can manage accounts and UI. Registered
users can edit their information using their login credentials. Customer can generate the
cart according his requirement. Guest can search the record according to requirement
As far as the future perspective is concerned, the scope of improvement would be

development in UI, better searching facilities.
3.2 Product Functions
1) A Home page with product catalog

This is the page where the user will be navigated after a successful login. It will display all
the book categories It also includes some special sections like recent arrival, about us and
contact us.
2) Book Description
If the user would like to know details about a book he can click on the title from where he
will be directed to a Book description page.
3) Shopping Cart
The user can manage a shopping cart which will include all the books he selected. The user
can edit, delete and update his shopping cart. A final shopping cart is a summary which
includes all the items the user selected and the final total cost.
4) Managing User Accounts
Each user should have an account to access all the functionalities of website. User can sign in
using login page and sign out using the logout page. All the user sessions will be saved in the
database.
5) Administration
The Administrator will be provided with special functionalities like
 Add or delete a book category
 Add or delete a member.
 Manage member orders.
This product is mainly designed to keep the information about the alumni and event
organized for alumni. There will be 4 users of the system-administrator, counselor,
placement officer, and alumni. Each user will be provided a login id and password to
interact with the system.
3.3 User Characteristics
The main users of this system will be Administrator, Registered User and Guest who are
literate with the computers and can use the programs such as Internet explorer, editors
and text processors.
3.4 General Constraints
The “Online Book Store” should run on all Internet Browser and all processors which
supports the Internet Browser.
5
4. REQUIREMENTS
4.1 FUNCTIONAL REQUIREMENTS
4.1.1 On-Line Alumni Record Entry:
U1: Alumni
There is an entry interface that is intended to facilitate the user (Administrator, Alumni)
to enter record in the Alumni database. User has to enter various fields information
(Name, Parents address, current location, email Id etc)
Scenario 1: Mainline Sequence

1.Administrator/Alumni: select record entry option.
2.System: Display form to enter the records.
3.Administrator/Alumni: Enter the necessary records.
4.System: Put the corresponding records in Alumni database.
5.Administrator: select the event generation option
6.System: Store event in the database.
6
U2: Follow up based on result of search Engine and Event<counselor>
Depending on the event, Counselor fire query on the Alumni database to get the list of
the Alumni to inform them about the event and mark the follow up. Counselor can
search the records according to batch, location etc.

1.Counselor: Select the search criteria.
2.System: Display the Alumni records as per the search criteria.
3.Counselor: Send the event information to the respective Alumni and mark the follow
up.
U3: Fire query for search<Placement Coordinator>

Depending upon the requirement, The Placement Co-ordinator will fire the query on the
Alumni Database. The searching criteria depend on company requirement. The
Placement Co-ordinator search depending upon Experience, Key Skills.

1.Placement Coordinator: Select the search criteria.
2.System: Display the Alumni records as per the search criteria.
3.Placement Coordinator: Save the Alumni record in XML or in Excel and Send the
information to the respective Company.
U4: Edit Alumni Record<Alumni>

Alumni will be assigned a default user Id and password, using this user Id and Password,
Alumni can login and edit their information. Alumni will get the information about the
events.

1.Alumni: Login to their account.
2.System: Display the corresponding event information.
3.Alumni: Select the edit information option.
4.System: Allows Alumni to update the information and save it back to the central
database.
4.1.2 Administrator Record Entry:
7
U1: Enter, Edit record and Event generation:
There is an entry interface that is intended to facilitate the Administrator to enter record
in the Alumni database. Administrator has to enter various fields’ information (Name,
Parents address, current location, email Id etc). Administrator can generate the events.
Scenario 1: Mainline Sequence:

1.Administrator: select record entry option.
2.System: Display form to enter the information.
3.Administrator: Select the event generation option.
4.System: Store event in the database.
U2: Store the information in the database:

Administrator has the authority to store the alumni records using either Excel sheet, XML
or using form.

1. Administrator: Select, store Alumni information, option
2.System: Display three options (Excel, XML, Form)
3. Administrator: Choose one option.
4.System: Store according to selected option.
U3: Generate Default Id and Password:

Administrator has the authority to generate default Id and password for Alumni.with the
help of this default Id and password Alumni can access their account and update their
information.

1. Administrator: Select, Generate User Account, option.
2.System: Based on the information available in database about the Alumni, system will
generate the default user Id and password for the respective Alumni.
4.1.3 Placement Record Entry:
8
U1: Search based on different criteria’s:
This is an interface that is intended to facilitate the Placement officer to obtain results
based on the search criteria given by him such as name, surname, domain, experience,
location, etc.
As well as to convert the obtained list according to the certain criteria’s in to the excel
sheets or XML document.

1.Placement officer: Select search option.
2.System: Display the form for searching records.
3.Placement officer: Select the search criteria such as name, surname, domain,
experience, location, etc.
4.System: Display the list according to search query.
U2: Converting output in excel sheet or XML:

The output, based on the search criteria, will be converted into desired format
(Excel or XML).

1. Placement officer: Select the link to convert search result in to excel sheets or XML
document.
2.System: Convert obtained list (result obtained with help of search engine) in to excel
Sheets or XML document.
4.1.4 Alumni Record Entry:
U1: Edit Alumni Profile:

For the first time alumni will log on with the help of given default ID and password. And
then he/she will be able to change password and edit his/her information.

1.Alumni: Edit the profile.
2.System: Store the edited information in the database.
9
U2: Change Password:
Alumni can select the change password option and can save the changed password back
to centralized database.

1.Alumni: Select, Change Password, option.
2.System: Store the changed password in the database.
5.Design:
5.1 Database Design
The following table structures depict the database design.

Table1: AlumniInfo
Key Type/ Column Name Data Type Length Allow Null

Constraint (1=Yes;0=No)
pk Registration_No Varchar 20 0
First_Name Varchar 200 0
Middle_Name Varchar 50 1
Last_Name Varchar 50 1
Gender Varchar 10 0
DOB_Date Varchar 50 0
DOB_Month Varchar 50 0
DOB_Year Varchar 50 0
Branch_Id Int 4 0
Employeement_Status Int 4 1
Current_Organization Varchar 50 1
Current_Address Varchar 300 1
Current_City Int 4 1
Current_City_Other Varchar 50 1
Current_State Int 4 1
Current_State_Other Varchar 50 1
Current_Country Int 4 1
Current_Country_Other Varchar 50 1
Email_Id1 Varchar 50 1
Current_Phone1 Varchar 200 1
Permanent_Address Varchar 50 1
Permanent_City int 4 1
Permanent_City_Other Varchar 50 1
Permanent_State Int 4 1
Permanent_State_Other Varchar 50 1
Permanent_Country Int 4 1
Permanent_Country_Other Varchar 50 1
Permanent_Phone1 varchar 200 1
Current_Salary int 4 1
Ref.key Skill1 Int 4 1
Skill2 Int 4 1
10
Skill3 int 4 1
Skill4 Varchar 50 1
Skill5 Int 4 1
Skill6 Varchar 50 1
Total_Experience Int 4 1
Photo Varchar 100 1
Password Varchar 20 0
Batch_Id Varchar 20 0
Course_Id Varchar 20 1
Additional_Certification Varchar 200 1
Current_Designation Varchar 100 1
Previuos_Org1 Varchar 100 1
Experience1 int 4 1
Experience2 int 4 1
Experience3 int 4 1
Change int 4 1
Table2: Alumni StaffInfo

Pk User_ID varchar 20 0
Password varchar 10 0
Member_Name varchar 20 1
Disignation varchar 20 1
LastAccess varchar 25 1
Table3: Alumni EventInfo

pk Event_ID int 4 0
Description varchar 20 0
Event_Date varchar 15 1
Event_Status varchar 10 0
Event_Location varchar 20 0
Table4: Alumni_FollowUp

Pk,rf User_Id varchar 20 0
Pk,rf Event_Id int 4 0
11
Table5: _Alumni Albums

Pk Album_Id int 4 0
Ref Batch_Id varchar 20 0
Album_Date varchar 10 0
Table6: Alumni Course

Pk Course_Id varchar 20 0
Course _Name varchar 60 0
Duration int 4 1
Table7: Alumni Batch

Pk,ref Batch_ Id varchar 20 0
ref Course_Id varchar 10 0
Center_ID varchar 20 0
Year varchar 20 0
Table8: Alumni City
12
Pk Code varchar 50 1
City nvarchar 255 1
State varchar 50 1
Table9: Alumni State

Pk Code varchar 50 1
State varchar 50 1
Country varchar 50 1
Table10: Alumni Country

Pk Country varchar 255 1
Code varchar 50 1
Table11: Alumni Techno

Pk Tech_ID int 4 0
Tech_Name varchar 20 1
Table12: Alumni Photos

Pk Photo_Id int 4 0
Ref Album_Id int 4 0
Short_Image_URL varchar 100 0
13
Longe_Image_URL varchar 100 0
Table13: Alumni Branch

Pk,ref Branch_ID int 4 0
Branch_Name Varchar 20 0
Table14: Alumni_Center

Pk Center_ID varchar 20 0
Center_Name varchar 50 0
Center_Address varchar 100 0
Fax_Phone Varchar 15 0
Email_ID varchar 30 0
Home_Page varchar 50 0
Table15: Alumni_TempInfo
Key Type/ Column Name Data Length Allow Null

Constraint Type (1=Yes;0=No)
pk Registration_No Varchar 20 1
First_Name Varchar 200 1
Middle_Name Varchar 50 1
Last_Name Varchar 50 1
Gender Varchar 10 1
DOB_Date Varchar 50 1
DOB_Month Varchar 50 1
DOB_Year Varchar 50 1
Branch_Id Int 4 1
14
Employeement_Status Int 4 1
Current_Organization Varchar 50 1
Current_Address Varchar 300 1
Current_City Int 4 1
Current_City_Other Varchar 50 1
Current_State Int 4 1
Current_State_Other Varchar 50 1
Current_Country Int 4 1
Current_Country_Other Varchar 50 1
Permanent_Address Varchar 50 1
Permanent_City int 4 1
Permanent_City_Other Varchar 50 1
Permanent_State Int 4 1
Permanent_State_Other Varchar 50 1
Permanent_Country Int 4 1
Permanent_Country_Other Varchar 50 1
Current_Salary int 4 1
Ref.key Skill1 Int 4 1
Skill2 Int 4 1
Skill3 int 4 1
Skill4 Varchar 50 1
Skill5 Int 4 1
Skill6 Varchar 50 1
Total_Experience Int 4 1
Photo Varchar 100 1
Password Varchar 20 1
Batch_Id Varchar 20 1
Course_Id Varchar 20 1
Additional_Certification Varchar 200 1
Current_Designation Varchar 100 1
Experience1 int 4 1
Experience2 int 4 1
Experience3 int 4 1
C_Batch
Change int 4 1
Fields:
_strCourseID
_strBatchID
_strCenterID
Appendix A:
_strYear
Class Diagram:
Properties :
+BatchId
+CourseId
+CenterID
+Year
Methods:
+Delete() :bool 15
+GetAllBatchRecord():DataTable
+Insert():bool
+Update():bool
16
C_Course
Fields :
_intDuration
_strCourseId
_strCourseName
Properties :
+CourseId
+CourseName
+Duration
Methods :
+Delete():bool
+GetAllCourseRecord():DataTable
+GetAllCourseIds():DataTable
+Insert():bool
+Update():bool
C_User
Fields :
_staffName
_staffId
_username
_registrationId
_password
_acesstime
Properties :
+Password
+StaffName
+UserName
+StaffId
+RegistrationId
+LastAccessTime
Methods:
+C_User():void
+Validate(username :string,password :string ):bool
+Validate(username :string,password :string ,designation
:string):bool
+Update(staffId :string): bool
17
CSQLHelper
Fields :
connString
sqlcmd
sqlconn Database
sqlreaderFields :
Methods :
+ConnectionString
+CSQLHelper()
+Validate(p_user :string,p_password:string):bool
SQLHelper
Methods :
+ExecuteNonQuery(connstring
:string,cmdType:CommandType,cmdText:string,cmdParams[]
:SqlParameter) :int
+ExecuteNonQuery (conn :SqlConnection, cmdType :CommandType,

cmdText : string, cmdParms[] : SqlParameter) :int
+ ExecuteNonQuery(trans:SqlTransaction,cmdType :CommandType,
cmdText:string,cmdParms[]:SqlParameter):int
+ExecuteReader(connString:string,cmdType:Commandtype,
cmdText:string, cmdParms[]:SqlParameter):SqlDataReader
+ExecuteScalar(connString:string,cmdType:Commandtype,
cmdText:string, cmdParms[]:SqlParameter):object
+ExecuteScalar(connString:SqlConnection,cmdType:Commandtype,
cmdText:string, cmdParms[]:SqlParameter):object
+GetDataSet(connstring:string, cmdType:Commandtype,
cmdText:string, tabName:string):DataSet
_PrepareCommand(cmd:SqlCommand,conn:SqlConnection,trans
:SqlTransaction,cmdType:CommandType, cmdText:string,
cmdParms[]:SqlParameter)
C_Alumni
Methods:
+CAlumni()
18
IDataOperations
Methods:
+Delete():bool
+Update():bool
+Insert():bool
C_Album
Fields:
_intAlbumId
_strBatchId
_strDescription
_strAlbumDate
Properties :
+AlbumId
+BatchId
+Description
+AlbumDate
Methods:
+Delete() :bool
+GetAllAlbumRecord(p_BatchId:string):DataTable
+Insert():bool
+Update():bool
+GetAllAlbumID():DataTableC_Photo
+GetMaxId():DataTable
Fields:
_strDescription:String,
_strShortImageURL: String,
_strLongImageURL: String,
_intPhotoID:int,
_intAlbumID:int
Properties :
+AlbumID:int
+PhotoID:int
+Description:String
+LongImageURL:String
+ShortImageURL:String
Methods:
+Delete() :bool
+GetAllPhotoRecord(string
p_AlbumId):DataTable
+GetPhotoRecords(): DataTable
+GetLargePhoto(int p_PhotoId):DataTable
+GetNumberOfPhotos(string 19
albumId):DataTable
+Insert():bool
+Update():bool
20
CPlacementSearch
Fields:
_strFull_Name
_intCurrent_City
_intExperience
_intBranch_Id
_intSkill1
_intSkill2
_intSkill3 C_CreateAccount
_intSkill4
Fields :
Properties :
+Full_Name
_floatCurrent_Salary:float
+Branch_Id
_intBranch_Id:int,_intEmployment_Status:int,
+Current_City
_intCurrent_City:int,_intCurrent_State:int,
+Experience
_intCurrent_Country:int,_intPermanent_City:int,
+Skill1
_intpermanent_State:int,_intPermanent_Country:int, _intSkill1:int,
+Skill2
_intSkill2:int,
+Skill3
_intSkill3:int, _intSkill4:int, _intExperience:int,
+Skill4
_strRegistration_No:string,_strFull_Name:string,
Methods:
_strGender:string,_strDOB:string,_strOrganization_Name:string,
+Select():SQLDataReader
_strCurrent_Address:string,_strEmail_Id:string,
_strCurrent_Phone_No:string, _strPermanent_Address:string,
_strPermanet_Phone_No:string, _strPicture:string, _strPassword:string,
_strBatch_Id:string, _strCourse_Id:string
Properties IDataSearch
:
Methods:
+Batch_Id:string
+Select():SQLDataReader
+Brach_Id:int
+Course_Id: string
+Current_Address: string
C_Cities
+Current_City:int
+Current_Country:int
Methods:
+Current_Phone_No:string
+GetAllCityRecord():DataTable
+Current_Salary:float
+GetAllCityRecord(strState:string):DataTable
+Current_State:int
+GetCity(cityCode:string):string
+DOB:string 40
+Email_Id:string
C_EventSearchCriteria
+Employment_Status:int
Fields:
+Experience:int
_strYear
+Full_Name:string
_strSkills
+Gender:string
_strCity
+Organization_Name:string
_strExp
+Password:string
+Permenant_Address:string
Properties :
+Permenant_City:int
+Year
+Permenant_Country:int
+Skills
+Permenant_State:int
+City
+Permenant_Phone_No:string
+Exp
+Picture :string
Methods:
+Registration_No:string
+GetAllRecords(query:string):DataTable
+Skill1:int
+Skill2:int
+Skill3:int
+Skill4:int
Methods :
21
+Delete() :bool
+Insert():bool
+Update():bool
C_EventGeneration
Fields:
_strDescription
_strStatus
_strEvent_Location
_dt_Date;
_intEventID;
Properties :
+EventID
+Description
+EventDate
+EventStatus
+Event_Location
Methods:
+Delete() :bool
+Insert():bool
+Update():bool
+GetAllRecord():DataTable
+GetAllEvents():DataTable
+GetDescription():DataTable
22
C_Center
Fields:
_strCenterID
_strCenter_Name
_strCenter_Address
_strFax_Phone
_strEmail_ID
_strHomePage
Properties :
+CenterID
+CenterName
+CenterAddress
+FaxPhone
+EmailID
+HomePage
Methods:
+Delete() :bool
+GetAllCenterRecord():DataTable
+GetCenterIds():DataTable
+Insert():bool
+Update():bool
C_Countries
Methods:
+GetAllCountryRecord():DataTable
+GetCountry():DataTable
C_States
Methods:
+GetAllStateRecord ():DataTable
+GetState ():DataTable
23
C_ChangePassword
Fields:
_strPassword
_strRegistration_No
Properties :
+Password
+Registration_No
Methods:
+Delete() :bool
+Insert():bool
+Update():bool
C_Branch
Fields:
_intBranchID
_strBranchName
Properties :
+BranchID
+BranchName
Methods:
+Delete() :bool
+GetAllBranchRecord():DataTable
+Insert():bool
+Update():bool
24
Course Table Enters Alumni
Enters Admin data in
data in Table
Alumni
table Table
Registration_No
First_Name
Middle_Name
Last_Name
Gender
Batch Table DOB_Date
DOB_Month
DOB_Year
Course_ID Branch_Id
Employeement_Status
Course_Nam Current_Organization
e Current_Address
Current_City
Duration Current_City_Other
Current_State
Generat Current_State_Other
Current_Country
e Current_Country_Other
Batch_Id events Email_Id1
Email_Id2
Batch_Name Current_Phone1
Current_Phone2
Permanent_Address
Permanent_City
Permanent_City_Other
Permanent_State
Permanent_State_Other
User_ID EventInfo Permanent_Country
Permanent_Country_Other
Password Table Permanent_Phone1
Member_Nam Permanent_Phone2
Current_Salary
e Skill1
Skill2
Disignation Skill3
Skill4
Skill5
EventInfo Skill6
Total_Experience
Description Photo
Password
Batch_Id
Course_Id
Additional_Certification
Current_Designation
Previuos_Org1
Experience1
Previuos_Org2
Experience2
Previuos_Org3
Experience3
Change
25
Interfaces:
27
28
29
30
31
32
6. CODING STANDARDS IMPLEMENTED
6.1 Coding Standards as provided by the client.
Primitive Type Notation
Data Type Prefix
sbyte sy
short s
int i
long l
byte y
ushort us
uint ui
ulong ul
float f
double d
decimal dec
bool b
char c
Type Notations
Type Prefix
Boolean bln
Char ch
Double dbl
Exception ex
Integer int
String str
StringBuilder strb
DateTime date
Naming and Capitalization
Below summarizes the naming recommendations for identifiers in .Net. Pascal casing is used
mainly (i.e. capitalize first letter of each word) with camel casing (capitalize each word except
for
the first one) being used in certain circumstances.
Student Performance Monitoring System
Identifier Case Examples Additional Notes

Class Pascal Person, Class names should be
BankVault, based on
33
SMSMessage, "objects" or "real things"
Dept and
should generally be
nouns. No
‘_’ signs allowed. Do not
use
type prefixes like ‘C’ for
class.
Method Pascal GetDetails, Methods should use verbs

UpdateStore or
verb phrases
Parameter camel personName, Use descriptive parameter
bankCode names. Parameter names
should
be descriptive enough
that the
name of the parameter
and its
type can be used to
determine its
meaning in most
scenarios.
Interface Pascal with "I" IDisposable Do not use the ‘_’ sign
prefix
Property Pascal ForeColor, Use a noun or noun
BackColor phrase to
name properties.
Associated _camelCase _foreColor, Use underscore camel
private member _backColor casing for
variable the private member
variables
Exception Class Pascal with WebException,
"Exception" SMSException
suffix
Event Pascal plus VS uses underscores to
optional btnSubmit_Click, separate
"EventHandler Painting, Click, an object from its event.
" suffix where Clicked, Be
relevant MyEventHandler careful with tense
(pre/past), e.g.
a Close event that can be
canceled should have a
Closing
event and a Closed event.
MS
also recommend adding
the
"EventHandler" suffix
where
thought needed.
34
User Interface Objects and Controls
Control Prefix Example

Label lbl lblSurname
TextBox txt txtSurname
DataGrid dg dgResults
Button btn btnSave
ImageButton ibtn ibtnSave
Hyperlink lnk lnkHomePage
DropDownList ddl ddlCompany

ListBox lst lstCompany
DataList dlst dlstAddress
Repeater rep repSection
Checkbox chk chkMailList
CheckBoxList chk chkAddress
RadioButton rdo rdoSex
RadioButtonList rdo rdoAgeGroup
Image img imgLogo
Panel pan panSection
plh plhHeader
PlaceHolder
Calender cal calMyDate
Adrotator adr adrBanner
Table tbl tblResults
[All] Validators val valCreditCardNumber
ValidationSumm vals valsErrors
ary
lvStudentList
ListView lv
DataGridTableSt dgts dgtsTable
yle
DataGridTextBo dgtbc
xColumn dgtbdName
DataReader dreader dreaderValue
DataRow drow drowTime
DataSet dset dsetValue
DataTable dtable dtableStudent
Mainmenu mm mmFile
MenuItem mi miNew
PictureBox pbx pbxPhoto
SDI-Form form
formEmployee
SqlCommand sqlcom sqlcomQuery
SqlCommandBui sqlcomb sqlcombQuery
lder
SqlConnection sqlcon sqlconQracleConnection
SqlDataAdapter sqlda sqldaData
stb stbMyStatusBar
35
StatusBar
TabControl tabctrl tabctrlInfo
TabPage tabpage tabpageColor
ToolBar tbr tbrMyToolBar
ToolBarButton tbb tbbFileNew
Timer tmr tmrExam Counter
Namespaces
All namespace should use Pascal casing and be prefixed with your company (and department
if
you wish). See examples below:
Sample "project level" namespaces:
YourCompany.YourDept.YourProject
Visualize.Blog
Generic reusable routines, classes etc which will be used across projects, can sit at the
'company'
or 'dept' level, for example:
Visualize.Utils
Comments:
· Comment each type, each non-public type member, and each region declaration.
· Use end-line comments only on variable declaration lines. End-line comments are
comments that follow code on a single line.
· Separate comments from comment delimiters (apostrophe) or // with one space.
· Begin the comment text with an uppercase letter.
· End the comment with a period.
· Explain the code; do not repeat it.
6.2 Standards used for User Interface Design.
Name of Size Font Name

Controls
Label 8x Verdana
Textbox 10 pts Verdana
Button 8 pts Microsoft Sans Serif (Bold)
Label 18 pts Verdana (Bold)
7. TEST REPORT
Another group called Sun MicroSystems did the testing and the report of the testing
is given
Here under.
36
Project Name :- Alumini Tested By - Sun Microsystem

Management System group (SUNBEAM)
37
Type of Error
Test case
Sr. No Expected Result Actual Result Error Message (Syntax /
Description
Logical)

Headings are according

Headings of Coloumns Proper names
1 Failure to that given in Syntax Error
of GridView expected
database
No proper message
Should allow to
Entering the duration specifying whether
2 enter integer Failure Syntax Error
for the course duration is in month or
values
year.
Should allow to If entering a value

Entering the duration
3 enter integer Failure above 12,it shows error Syntax Error
for the course
values message.
No proper validations
Entering values for Should allow to done for the
4 Course-ID and Course enter only proper Failure fields.Allowing entering Syntax Error
Name values. of integer values for
Course Name
Check for sorting Should allow Sorting facility not

5 Failure Error
facility in GridView sorting provided
On clicking
Selecting a particular
Reset,the data of No action taken on the
6 record from GridView Failure Logical Error
all enabled fields click of button
for editing
should get cleared
Check for paging Should allow Paging facility not

7 Failure Error
facility in GridView paging provided
Clicking on Save Should give error No error message if

8 button while the fields message for blank Failure duration field is left Logical Error
are blank fields blank
Clicking on Save Should give error Error not handled

9 button with only message for blank Failure properly which leads to Logical Error
Duration field blank field error page with the
38
error--Input String was
not in correct format.
Should allow
Error not handled
entering such
Adding a New Course properly which leads to
characters and if
10 Name containing '&' Failure error page with the Logical Error
not,then proper
symbol. error--Input String was
message should
be given for that.
It should give
appropriate
There is no notfication message when Logical Error.
11 or *marks for compulsary fields No message Validation
compulsory Fields are empty on required.
create Alumni
account page
It should give
appropriate Logical Error.
Validating Permant
2 message when No message Validation
Address Field
inpttting numeric required.
values
It should give
appropriate Logical Error.
Validating Current
3 message when No message Validation
Address Field
inpttting numeric required.
values
After edition while
saving information
by clicking save
Displaying appropiate button appropiate Validation
12 No message
Message message should Required.
be give wether
record saved or
not
In Personal
Information there
Validating Date Of should give Validation
13 No message
Birth Field proper message if Required.
this field will not
selected
After clicking Next
button on Contact
Validating Contact Validation
14 Information page No message
Information Field Required.
it should give
proper message
39
when compulsary
fields are empty
It should give
appropriate
message when
Validating Branch Id Validation
15 compulsary fields No message
Field Required.
are empty on
create Alumni
account page
After edition when Redirection

information get Facility to
saved then page Generate
No Redirection
16 Redirecting Facility should be Account
Facility
rediercted to should be
Generate Account present from
page edit page.
After Clicking
Generate
Displaying appropiate Accounts button Validation
17 No message
Message appropiate Required.
message should
be disply
It should give
appropiate
Logical Error.
Validataing PhoneNo message when
18 No message Validation
Field string value
required.
entered in the
field
It should give Working of

Working of Generate message for Generate
19 No message
Accounts Button duplication of Button not
record proper.
40
database
Error not handled

Should allow to properly which leads to
21 Entering Photo Details enter only proper Failure error page with the Syntax Error
values error--Input String was
Should Reset all

22 Reseting the fields Failure Doesn't Work Logical Error
the fields
Browsing For Photo at

Should update the
23 Updating The Photo Failure the time of updating is Logical Error
photo
not Provided

24 Failure Error

25 Failure Error
After entering the

selecting
respective data
Reset Button is not No Specific Error is
26 we can reset all No Failure Error
Working generated
the fields by
clicking reset
button
If user enters
wrong information
No Specific Error is
27 No Edit Fuctionality or data then user No Failure Error
generated
can not edit in
same page
If no Single Field If User select single

is select and user field then validation is
Save Button clicks on save working but if no field is
28 Failure Runtime Error
Functionality button then select then validation
runtime error is work sometimes and
genrated sometimes it not
41
working
Paging should be
done with
No Paging is Done On gridview is No Specific
29 No Failure Lack of Functionality
GridView information is Error
large then it is to
manage by paging
After submitting
Index count must refer
Submitting form this proper
30 Failure to location within the Logical Error
without selecting fields message is
string.
diaplayed.
For selecting
In this default
field default
31 Description text field select text is not No error Error
select should
displayed.
be present.
According
description field Fields are not enabled
If description field is
32 the other fields Failure or disabled according to Logic Error
selected
are enabled or field
disabled.
According to this
If Genrate mail ID
34 mail Id should be Exception Error Error
Button is Clicked
genrated
According
If Send mail Button is selected field mail
35 Failure No error message Not working
selected should be send to
appropriate field.
The checking of
duplication of
'Event ID' Should No Error Message,But
Checking Of '.cs File'
36 not be done as it Failure checking for the same
for logical Error. Logical Error.
is autogenerated is done.
and user cant
enter it or update
42
it.
Proper
Commenting
should be
37 Checking Commemts. Failure
provided,atleast Syntax error
15% of total
coding.
Extra spacing is found

Line Spacing at most of the
Checking For
38 should be uniform Failure places,like in the code Syntax Error
Indentation
. of Save button event
handling.

database
At the Time Of Editing it

Proper Validation
40 Entering Date Failure Shows Unexpected Logical Error
Expected
Result
Should Reset all

41 Reseting the fields Failure Doesn't Work Logical Error
the fields
Checking Date For Should Take Valid

42 Failure Take Invalid Date Logical Error
Date Format day and Month

43 Failure No Error

44 Failure No Error
Check For The Batch Should Take if Not Selected it take

45 Failure logical Error
id Proper Batch id --Select-- As it is
Error not handled

Check For the Should Take
46 Failure properly so that Logical Error
Description multiline Data
exception occurred
After Entering all

Entering All Details Of information and Format Exception Is
47 New Event 'FairWell clicking on save Failure Not Handeled By Tye Exception
Party'. button, record User.
should be inserted
43
in database and
immediately
shown in Grid-
View.
No Error Message .
Date Should Get Functionality
Editing The Date Of But,In the text box of
48 Changed Failure Error/Logical
The Event date new value can
Accordingly. error.
not be inserted.
A message such System.Format

as "Please Enter Exception
Entering Date in Date In correct The string was not
49 wrong format while Format!" should Failure recognized as a valid
Exception
adding New event. be given using DateTime. There is a
expression unknown word starting
validator. at index 0.
An Error message
Th 'Location' is not such as'Please String was not
50 selected and clicked select the Failure recognized as a valid
Exception
the save button. Location' should DateTime.
be given to user.
An Error message
Th 'Event status' is
such as'Please String was not
not selected and
51 Select the Event Failure recognized as a valid
clicked the save Exception
status' should be DateTime.
button.
given to user
An Error message No Error Message

such as'Event but,Same record get
Inserting Same record
52 Exist Already' Failure inserted again.There
again. Logical Error.
should be given to is a redundant data in
use database.
Project Name :- Alumini Management System

Prepared By:- Sun Microsystem group (SUNBEAM)
44
Sr. No Deviation In which programs
1 Comments are not inserted PhotoDetails.aspx(throughout page)
2 Comments are not inserted photo.cs

3 Proper Commenting not done CreateAccount.aspx.cs
4 Single Comment is not found AlbumDetails.aspx.cs
5 There are not proper identation AlbumDetails.aspx.cs
6 Comments are not inserted Album.cs
Proper Commenting should be provided,atleast
8 Checking Commemts.
15% of total coding.
9 Checking For Indentation Line Spacing should be uniform .
45

Sunbeam Institute of Information Technology: A Project On "Online Book Store"

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Sunbeam Institute of Information Technology: A Project On "Online Book Store"

Caricato da

Copyright:

Formati disponibili

A PROJECT ON

“Online Book Store”

SUNBEAM INSTITUTE OF INFORMATION TECHNOLOGY

2. Product Overview and Summary

4.1 Functional Requirements

4.2 Non-Functional Requirements

6. Coding Standards Implemented

8. Project Management Related Statistics

The software Library Management System has four main modules.

 Insertion to Database Module – User friendly input screen

2.3 References: www.oxfordbookstore.com, http://google.com

3.1 Product Perspective:

As far as the future perspective is concerned, the scope of improvement would be

3.2 Product Functions

1) A Home page with product catalog

3.3 User Characteristics

3.4 General Constraints

4.1 FUNCTIONAL REQUIREMENTS

4.1.1 On-Line Alumni Record Entry:

Scenario 1: Mainline Sequence

Scenario 1: Mainline Sequence

U3: Fire query for search<Placement Coordinator>

Scenario 1: Mainline Sequence

U4: Edit Alumni Record<Alumni>

Scenario 1: Mainline Sequence

4.1.2 Administrator Record Entry:

Scenario 1: Mainline Sequence:

U2: Store the information in the database:

Scenario 1: Mainline Sequence:

U3: Generate Default Id and Password:

Scenario 1: Mainline Sequence:

4.1.3 Placement Record Entry:

Scenario 1: Mainline Sequence

U2: Converting output in excel sheet or XML:

Scenario 1: Mainline Sequence:

4.1.4 Alumni Record Entry:

U1: Edit Alumni Profile:

Scenario 1: Mainline Sequence:

Scenario 2: Mainline Sequence

5.1 Database Design

The following table structures depict the database design.

Key Type/ Column Name Data Type Length Allow Null

Table2: Alumni StaffInfo

Key Type/ Column Name Data Type Length Allow Null

Table3: Alumni EventInfo

Key Type/ Column Name Data Type Length Allow Null

Key Type/ Column Name Data Type Length Allow Null

Pk,rf User_Id varchar 20 0

Pk,rf Event_Id int 4 0

Key Type/ Column Name Data Type Length Allow Null

Ref Batch_Id varchar 20 0

Table6: Alumni Course

Key Type/ Column Name Data Type Length Allow Null

Course _Name varchar 60 0

Table7: Alumni Batch

Key Type/ Column Name Data Type Length Allow Null

Pk,ref Batch_ Id varchar 20 0

ref Course_Id varchar 10 0

Table8: Alumni City

City nvarchar 255 1

Table9: Alumni State

Key Type/ Column Name Data Type Length Allow Null

Table10: Alumni Country