Sps Projectn Report

8/16/2019 Sps Projectn Report

1/69


2/69

INTRODUCTION


3/69

INTRODUCTION

The task of developing this project has been carried out in project BCA. This gives us the

advantages of knowing flipkart environment. The project entitled ”ONLINE FLIPKART ” has

been developed as per the reuirements of a customers .

ABOUT THE CLIENT:-

*nline flipkart is designed and developed for ABC flipkart. #n this project there will be

more than customer+s ,Client+s-(ome workers " a one particular manager. This is the one of the

best and popular flipkart in whole ha/ipur it will be earn per year 0C1 rupees. The project

entitled” ONLINE FLIPKART” has been developed as per the reuirements of address .

ABOUT THE PROJECT :-

The online flipkart will be provide very smooth an error free solution for every client who

will be join to website of this online flipkart. #t give every client free facility to registered

his reuirements and provide different services. #n this project a online flipkart provide every

customer to registered her whole reuirements for the different types of dresses. And then

manager check his registered form day by day and complete the reuirements of customers by

the help of home delivery. There will be one special choices for the customers that when the

delivery will not completed at write time than the manager provide his whole rupees and provide

the all demands that will be give n by him free facility.

The online flipkart provide has the different type of &odules2

0. Employee Module:2#t is used to maintain the structure facility and whole envouirmentof the flipkart.

3. Cu!ome" Module :- This module keeps details of the customers$ their personal

information$ about their shopping etc.

4. Boo#$%& Module :2 This modules is used for the booking system by the customers.. Del$'e"y Module:- This modules is used for delivered the reuirements of customers

at home.


4/69


5/69

I%$!$(l Re,u$"eme%!:-

INITIAL REUIRMENT


6/69

The following are the list of initial reuirements used in this document and the project as

well7

• Adm$%$!"(!o": A login id representing a user with user administration privileges to

the software• Ue": A general login id assigned to most users.

• M) ACCE)): (tructured 8uery 9anguage: used to retrieve information from a

database.

Ue". "e,u$"eme%!:-

H("d/("e "e,u$"eme%!:-

!ardware which supports ;in $ ?B26.@ and &.(. Access.

0$u(l B($*:-

?isual basic is the method which enable user to create graphical user

interface application. it is developed by M$*"oo1! Co"po"(!$o% of U2)2A2 #t is a

package or language to create graphical user interface application.

M2)2 A**e:-

A database is a collection of information that+s related. Access allows you to

manage your information in one database file. ;ithin access there are four major

areas7 T(+le3 ue"$e3 Fo"m (%d Repo"!2

Table store your data in your database.

8ueries ask uestions about information stored in

your table. 1eports allow you to print data based on ueries =

tables that you have created.


7/69

)y!em A%(ly$


8/69


9/69

#n the world we are growing for globali/ation day by day with the development in #T

resources and advancement$ by using latest technologies every organi/ation wants to beat its

competitors and want to grow. %nterprise 1esourceful Planning is the need of today+s

organi/ation. (urvival on manual system is difficult so$ that+s why organi/ation of the corporate

world wants to computeri/e their departments. The modules should be complete database driven

and interactive that should provide the proper information about the Placement and Training

*rgani/ation. (uccess of any system depends up to a large etent on how accurately a problem is

defined$ thoroughly investigated and properly carried out to the choice of solution. Analysis is

the only phase in which the reuirements for the new system are identified. (ystem analysis is a

detail study of the various operations performed by a system and their relationship within and

outside of the system. The uestion is7 what must be done to solve the problem *ne aspect of

analysis is defining the boundaries of the system and determining whether or not a candidate

system should consider other related system. 'uring analysis data are collected on the available

files$ decision points and transactions handled by the parent system. 'ata flow diagram$

interviews$ onsite observations$ uestionnaires are used as a logical system model and tools to

perform the analysis.

O+4e*!$'e o1 P"o4e*!

This software helps customer to find different all shopping$ their features$ and new updates

easily. #t is designed such a way that one can view all the updates of the (hopping from any

place through online. The software will help in easy maintaining and updating products in the

website for the administrator.

The project brings forth current method and techniues used in the 1euirement. (pecification of

information system. The highlight here has been the use of various modal to define system scope$

domain analysis$ functional behavior$ system timing$ and object definition " design.


10/69

The problem in shopping information system is dealing with the )lipkart (hopping between

database design and process design. 'esigning= mobile the database and designing= *nline

(hopping the software are often treated as separate processes.

The main objectives of this project of the new system are mentioned below2

5. )ast and efficient.

6. 1eliable and accurate.

7. Centrali/ed 'ata.

82 on 1edundant #nformation.

92 %asy to Access.

LIMITATION) OF EI)TIN; )


11/69

0. The use of man power in this so high.

3. 8uick report on the current status will be very time consuming and the chances of error

will be high.

4. eed a lot of paper work.

P"opoed )y!em

Proposed system is an automated *nline )lipkart (hopping. Through our software user can

(hopping. ;ebsite admin to update information$ edit information .*ur proposed system has the

following advantage.

• Eser friendly interface.

• )ast access to database.

• 9ess error.

• &ore (torage Capacity.

8uick response.

Be%e1$!:

*nline shopping makes all the difference when it comes for the mobile products .#t not

only allows buying best products within your parches for the new Product of all shopping .The

best thing about online shopping$ is not just only offers the widest selection but also the

everything in your budget.

Co! Be%e1$! A%(ly$:-

Cost Benefits analysis is performed to ascertain whether the costs in the system match

with the benefits they will provide. The various end of costs incurred in the development and

implementation of the system include7


12/69

!ardware costs incurred in purchase of hardware$ i.e.$ computer and its

peripherals.

Personnel cost include the salaries of the %'P staff as well as the perks of

personnel involved in the development of the system. )acility costs are epenses incurred in the preparation of the physical site

like flooring$ wiring$ lighting etc. *peration costs include all costs associated with the day2to2day operation of

the system. (upply costs are variable costs that increased use of paper$ ribbon$ disks etc.

The system is epected to provide benefits. The first is to identify each benefit

and then assign a monetary value to it for cost=benefit analysis. Both tangible

and intangible benefits are considered as discussed earlier.

P"o*edu"e 1o" Co!-Be%e1$! A%(ly$:

• The determination of cost and benefit can be enumerated as under7

#dentify the various costs and benefit pertaining to give project.

Categori/e the various costs and benefits for analysis.

(elect and method for evaluation.

#nterpret the results of evaluation.

Take action.

Ad'(%!(&e:-

0. All the procedure in this project is automatic accept the of data from the user.

3. The project given the user2friendly environment$ which gives the way of working in

more efficient manner.

Fe($+$l$!y )!udy

;hen a project is started an initial investigation is carried out. 'uring this

phase of study users need has recogni/ed and other reuirements are determined.


13/69

*nce the problem has been defined a study is carried out to select the best

system i.e. a feasible system that means performance reuirements. (o )easibility is the

determination of whether or not a project is worth doing and the process followed

in making this determination is called a )easibility (tudy. #n order to conduct the

feasibility study we have seven distinct$ but inter2related types of feasibility$ These

are Technical feasibility$ *perational feasibility$ %conomical feasibility$ (ocial feasibility$

&anagement feasibility$ 9egal feasibility and Time feasibility. *ut of these seven three

are key feasibilities to consider$ these are7

• Technical )easibility

• %conomical )easibility

• *perational )easibility

Te*=%$*(l 1e($+$l$!y:-

This is concerned with specifying euipment ,hardware- and software that will successful

satisfy the user reuirement. #t considers the following facts:

• The facility to produce outputs in a given time

• 1esponse time under certain conditions

• Ability to process a certain volume of transaction at a particular speed

• )acility to communicate data to distant location

;hile eamining technical feasibility$ huge importance is given to the configuration of the

proposed system. The configuration should give the complete picture about the system+s

reuirement such that what kind of hardware is reuired and how these units are

interconnected .The proposed system can be run on currently eisting software and hardware.

E*o%om$*(l 1e($+$l$!y:-

(ince cost plays uite an important role in deciding the new system$ it must be identified

and estimated properly. (o economic analysis is the most freuently used techniue for

evaluating the effectiveness ,economical feasibility- of a proposed system. To determine the

economical feasibility of the system a cost=benefit analysis is to make. This procedure is


14/69

to determine the benefits and savings that are epected from a proposed system and

compare them with costs. )our facts that plays an important role in deciding economical

feasibility of the proposed system are as follows7 Cost2saving benefits$ Cost2avoidance

benefits$ #mproved2performance benefits$ #mproved2information benefits$ !ence the proposed

system is economically feasible.

Ope"(!$o%(l 1e($+$l$!y:-

#t is mainly related to human organi/ational aspects. The points to be considered are7

• ;hat changes will be brought with the system

• ;hat organi/ational structures are disturbed• ;hat new skills will be reuired

'o the eisting staff members have these skills if not$ can they be trained. The project would be

beneficial because it satisfies the objectives when developed " installed. All operational aspects

are considered carefully " conclude that the project is operationally feasible.


15/69

)o1!/("e "e,u$"eme%!

pe*$1$*(!$o%


16/69

)o1!/("e "e,u$"eme%! pe*$1$*(!$o%

A reuirements specification for a software system F is complete description of the behavior of a

system to be developed. #t includes a set of used cases that describe all the interactions the users

will have with the software. #n addition to use cases$ the (1( also contains non2functional ,or

supplementary- reuirements. on2functional reuirements are reuirements which impose

constraints on the design or implementation ,such as performance engineering reuirements$

uality standards$ or design constraints-.1euirement documentation is very important

activity after the reuirements elicitation and analysis. This is the way to represent the

reuirements in a consistent format. 1euirement document is called )o1!/("e Re,u$"eme%!

)pe*$1$*(!$o% >)R)?2

The software reuirement specification is produced at the culmination after analysis task.

This is the way to represent reuirements in a consistent format. #t is a specification for

a particular software product $ program or a set of programs that performs certain

functions in a specific environment .The function and allocated to software as part of

system engineering are refined by establishing a complete information description$ a

detailed functional and behavioral description$ an indication of performance reuirements

and design constraints$ appropriate validation criteria$ and other data pertinent to

reuirements.

(oftware product$ program or set of programs that perform certain functions in a specific

environment. There are two important cases regarding (1(7 )irst one$ (1( is used to

define the needs and epectations of the users. The second one$ (1( is written for different

purpose and serve as a contract document between customer and developer. This

produces the probability of the customer being disappointment with the final product.

#%%% defines a reuirement as7

A condition of capability needed by a user to solve a problem or achieve an

objective.

http://en.wikipedia.org/wiki/Use_casehttp://en.wikipedia.org/wiki/Non-functional_requirementshttp://en.wikipedia.org/wiki/Performance_engineeringhttp://en.wikipedia.org/wiki/Quality_(business)http://en.wikipedia.org/wiki/Non-functional_requirementshttp://en.wikipedia.org/wiki/Performance_engineeringhttp://en.wikipedia.org/wiki/Quality_(business)http://en.wikipedia.org/wiki/Use_case


17/69

A condition or capability that must be met or processed by a system to satisfy

a contract$ standard$ specification$ or other formally imposed document.

enerally$ the (1( is a document that completely describes what the proposed software

should do without describing how the software will do it. The basic goal of the

reuirements phase is to produce the (1($ which describe the complete eternal

behavior of the proposed software.

O"&(%$@(!$o% o1 (% )R)

The most general organi/ation of an (1( is as follow7

I%!"odu*!$o%:-

This site will provide the mobile product process online.

Pu"poe:

%asy access and reduce limitation of eisting system.

)*ope:

#t will give the great help for the keep us update with product.

De1$%$!$o%:

ot applicable.

)y!em O'e"'$e/:

This system will be used by users buy the product.

O'e"(ll De*"$p!$o%:

#t will provide the online facility for buying for product.

P"odu*! Fu%*!$o%:

#t provide online mobile shopping for buying mobile product.

Ue" C=("(*!e"$!$*:

Administration$ users2

Co%!"($%! Aump!$o% (%d Depe%de%*$e:

)ast ecess and responsive.


18/69

'ependency on window platform and web

browser.

E!e"%(l $%!e"1(*e:-

•!ardware reuirement

• (oftware reuirement

Fu%*!$o%:-

• Eser can search baby product.

• Eser cans also his=her view about the site.

• Eser =Admin can view the feedback.

• Admin can view=post=edit=update=the product and add baby product.

Pe"1o"m(%*e "e,u$"eme%!:

%asy and )ast access.

Lo&$*(l d(!(+(e "e,u$"eme%!:

&( access.

De$&% *o%!"($%!:

Eser friendly and easy access to users and viewer. (uitable page

management for product.

Fe(!u"e:-

An (1( must consist of following features72

• Consistent

• Complete

• Enambiguous

• &odifiable

• ?erifiable

•Traceable

• 1anked

Pl(!1o"m:

;indows is very powerful scalable *perating (ystem that Provide basic file and prints

services as well as robust for server application.


19/69

&ain features are follows72

&ore etensive network management features.

#mproved network Performance.

%nhanced communication features.

Need 1o" )R):-

The (1( is needed for the following reasons72

D An (1( establishes the basis for agreement between client and developer.

D An (1( provides a reference for validation of the final product.

D A high2 uality (1( is a prereuisite to highFuality software.

A high2 uality (1( reduces the development cost.

O+4e*!$'e:2

A software reuirement specification is literally the conversation of a specific point. #tGs

difficult in this instance to avoid the circular reference. A projectGs specifications consist of the

body of information that should guide the project developers$ engineers$ and designers through

the work of creating the software.

A software reuirement specification document describes how something is supposed to

be done. A specifications document may list out all of the possible error states for a

certain form$ along with all of the error messages that should be displayed. The

specifications may also describe the steps of any functional interaction$ and the order in

which they should be followed by the user.

A reuirements document$ on the other hand$ would state that the software must handle

error states reasonably and effectively$ and provide eplicit feedback to the users. The

specifications show how to meet this reuirement.

(pecifications may take several forms. They can be a straightforward listing of functional

attributes$ they can be diagrams or schematics of functional relationships or flow logic$ or

they can occupy some middle ground. (oftware 1euirement (pecifications can also be

in the form of prototypes$ mockups$ and models. Project specifications are much more


20/69


21/69

Re,u$"eme%!:-

The software reuirements specification is produced at the culmination of the analysis

task. This is the way to represent reuirements in a consistent format. #t is a

specification for a particular software product $ program or a set of programs that

performs certain functions in a specific environment .The function and allocated to

software as part of system engineering are refined by establishing a complete

information description.

A detailed functional and behavioral description$ an indication of performance

reuirements and design constraints$ appropriate validation criteria$ and other data pertinent to

reuirements.

Fu%*!$o%(l Re,u$"eme%!:-

)unctional reuirements define the internal workings of the software7 that

is$ the calculations$ technical details$ data manipulation and processing$ and other

specific functionality that shows how the use cases are to be satisfied. #t also

contains nonfunctional reuirements$ which impose constraints on the design or

implementation ,such as performance reuirements$ uality standards$ or design

constraints-.

The name$ summary and rationale of each functional reuirement are used in the same way as

those of the use cases. The behavior that is to be implemented should be described in plain

%nglish in the J1euirementsK section most reuirements are only relevant to a small number of

use cases2these should be listed by name and number in the J1eferencesK section. ,(ome

reuirements are not associated with use cases.-The core of the reuirement is the description of

the reuired behavior. #t is very important to make this clear and readable. This behavior may

come from organi/ational or business rules$ or it may be discovered through elicitation sessions

with users$ stakeholders$ and other eperts within the organi/ation. &any reuirements will be

uncovered during the use case development. ;hen this happens$ the reuirements analyst should

create a placeholder reuirement with a name and summary$ and research the details later$ to be

filled in when they are better known2


22/69

#t deals with the functionalities reuired from the system which are as follows7

D The website will help the people to conduct their online buying product.

D *nly authori/ed person can access related detail.

D Administrator will be responsible for updating the site.

)e*u"$!y Re,u$"eme%!:-

(ecurity reuirements are the particularly significant in defense system and many

database systems. (ecurity reuirement place restrictions on the use of certain

commands$ control access to data$ provide different kind of access reuirement for

different people$ reuire the use of passwords and cryptography techniues$ and maintain

a log of activities in system. iven the current security needs even of common systems$

they may also reuire proper assessment of security threats$ proper programming

techniues$ and use of tools to detect flaws like buffer overflow.

)or the purpose of security process # have added the login feature into my project so as to keep it

safe from the eternal problem. *ne can only interact with my project by giving it the suitable

i.e. the accurate #' and password.

Ou!pu! Re,u$"eme%!:-

The output reuirements of the project are72

• Admin should have and id for 9ogin.

• There must be a output device for taking the

hard copy of any information.

)o1!/("e Re,u$"eme%!:-(oftware reuirement plays a very important role in the making the

development of a project$ as it provide a suitable language as well as the perfect medium to

implement our program or project on the system .(oftware reuirement is very necessary for the

implementation of a program. The software reuirements specification is produced at the


23/69

culmination after analysis task. This is the way to represent reuirements in a consistence format.

#t is a specification for a particular software product. Program or a set of program that perform

certain function in a specific environment. The function and allocation to software as part of

system engineering are refined by establishing a complete information description$ a detailed

functional and behavioral description$ an indication of performance reuirements and design

constraints$ appropriate validation criteria$ and other data pertinent to reuirements.

(oftware product$ program or set of program that perform certain function in a specific

environment. There are two important cases regarding (1(. )irst one$ (1( is used to define the

needs and epectations of the users. The second one$ (1( is written for different purpose and

serve as a contract document between customers and developer. This produces the probability of

the customer being disappointment with the final product.

H("d/("e Re,u$"eme%!:-

The hardware reuirement specification at the culmination of the analysis task.

This is the way to represent reuirements in a consistent format. #t is a specification for a

particular hardware product$ program or asset of programs that perform certain functions in a

specific manner.

#n the designation of my project hardware reuirement is also very necessary as it

provide various tools for the making of my project. ;hich supports development tools and web

browsers

Module De*"$p!$o%:-

Client in supported 1esidential (ervices ,(1(- have the same rights as anyone

else in the community2to be treated as an individual and to have his= her rights and values

respected. This module will give you an opportunity to eplore these issues$ as well your own practices in relation to your client+s autonomy$ dignity$ rights and value.


24/69

Module A$m:-

• *n successful completion of this session you should be able.

• 1ecogni/e how you developed your own values and how they can impact on

others.

• Enderstand the nature of self$ self2esteem$ self2worth$ dignity$ respect and

personhood.

• 1ecogni/e the practices can increase or reduce a client+s autonomy describe ways

in which you can support client+s autonomy$ dignity$ rights and values.

Fo"m Module:-

)orm module ,form file name etension- can contain tetual description of the

forms and its controls including their property setting. They can also contain form level

declaration of constants$ variables and eternal procedure and events and general procedure.

Cl( module:-

Class modules ,.cls file name etension- are similar to form modules$ ecept that

They have no visible user interface. Lou can use also modules to create your own object

including code for method and properties.

)!(%d("d module:-

(tandard modules ,.bas file name etension- can contain public modules leveldeclaration of type$ constants$ variables$ eternal procedures and public procedures.


25/69

)


26/69

)


27/69

same with waterfall development. *nce a phase of development is completed$ the development

proceeds to the net phase and there is no turning back.

The advantage of waterfall development is that it allows for

departmentali/ation and managerial control. A schedule can be set with deadlines for each stage

of development and a product can proceed through the development process. Theoretically$ be

delivered on time. 'evelopment moves from concept$ through design$ implementation$ testing$

installation$ troubleshooting$ and ends up at operation and maintenance. %ach phase of

development proceeds in strict order$ without any overlapping or iterative steps.

The disadvantage of waterfall development is that it does not allow for much reflection or

revision. *nce an application is in the testing stage$ it is very difficult to go back and change

something that was not well2thought out in the concept stage. Alternatives to the waterfall model

include joint application development ,MA'-$ rapid application development ,1A'-$ synchroni/e

and stabili/e$ build and fi problems.

The waterfall model is a seuential design process$ often used in software development

processes$ in which progress is seen as flowing steadily downwards ,like a waterfall- through the

phases of conception$ initiation$ analysis$ design$ construction$ testing$ production$

implementation "maintenance.


28/69

(!e"1(ll Model

Feasibility Study

Requireents analysis

and Speci!cation

"esi#n and

Codin# and Module

Testin#

$nte#ration and

odule testin#

"elivery

Maintenance


29/69


30/69

DE)I;NIN; APPROACH

Top do/% de$&%:-

The T*P '*; approach starts from the highest level component of the

hierarchy and proceed through to lower levels. A T*P '*; design approach start by

the major component of the system. 'ecomposing them into their lower level component

and iterative until the desired label of detail is achieved. Top down design method is in

some form of step wise refinement. (tarting from a abstract design in each step the designis refine to more concrete level$ until we reach a level were no more refinement is

needed.

A system consists of components$ which have components of their own: indeed a system is a

hierarchy of components. The highest level components correspond to the total system. The top

down approach from the highest level components of hierarchy and proceeds through to lower

levels. By contrast a bottom up approach starts with the lowest level component of the hierarchy

and proceeds through progressively higher levels to the top level components.

The T*P '*; approach has been promulgated by many researches and has been found to be

etremely useful for design. &ost design methodologies are based on the top down approach.

A T*P '*; approach suitable only if the specifications of the systems are clearly known and

the system development is from scratch. !owever$ if a system is to be built from an eisting

system$ a bottom approach is more suitable$ as it starts from some eisting components.


31/69

HI;H LE0EL

DE)I;N


32/69


33/69

T(+le N(me: 2 Baby Product

T(+le De*"$p!$o%: -Baby (hopping 'etails2

F$eld N(me

O" A!!"$+u!e

A!!"$+u!e

De*"$p!$o%

D(!(

Type

)$@e

C"o Re1e"e%*e

P"$m("y Key

1etailer #d #' of 1etailer ?arChar 0@ Primary Ney

ame ame of 1etailer ?arChar 0@ ot ull

Address Address of 1etailer ?arChar 0@ ot ull

Phone no. Phone no. of 1etailer umber 05 ot ull

%2mail id %2mail id of 1etailer ?arChar 05 ot ull

T(+le N(me:- (hop

T(+le De*"$p!$o%: 2(hop 'etails.

F$eld N(me

A!!"$+u!e

A!!"$+u!e De*"$p!$o% D(!( Type )$@e C"o Re1e"e%*e

O" P"$m("y Key

(hopOid (hopOid ?arChar 0@ Primary Ney

ame (hop ame ?arChar 3@ ot ull

Address Address of (hop ?arChar 4@ ot ull

Phone no. Phone no. of (hop umber 05 ot ull


34/69

T(+le N(me: - &arketing 1epresentative

T(+le De*"$p!$o%: -&arketing 1epresentative 'etails2

F$eld N(me

A!!"$+u!e

A!!"$+u!e De*"$p!$o% D(!( Type )$@e C"o Re1e"e%*e

O" P"$m("y Key

&1 id #' of the & 1 ?arChar 0@ Primary Ney

ame ame of the & 1 ?arChar 3@ ot ull

Address Address of & 1 ?arChar 0@ ot ull

&obile no. &obile no of & 1 umber 0@ ot ull

%2mail id %2mail id of & 1 ?arChar 05 ot ull

T(+le N(me:-Company

T(+le De*"$p!$o%: -Company 'etails2

T(+le N(me:-)eedback

T(+le De*"$p!$o%: -)eedback 'etails.

F$eld N(me

A!!"$+u!e

A!!"$+u!e

De*"$p!$o%

D(!( Type )$@e C"o Re1e"e%*e O"

P"$m("y Key

Company id #' of Company ?arChar 0@ Primary Ney

ame ame of the (tockiest ?arChar 0@ ot ull

Address Add of Ph. Company ?arChar 05 ot ull

%2mail id %mail id of Company ?arChar 0@ ot ull

Phone no. Phone no. of company o. 05 ot ull


35/69

F$eld N(me

A!!"$+u!e

A!!"$+u!e

De*"$p!$o%

D(!( Type C"o Re1e"e%*e O"

P"$m("y Key

ame ame of the user ?arChar ot ull

%2mail id %mail id of user ?arChar ot ull

(uggestion (uggestion of user Tet ot ull

?iew ?iew of user Tet ot ull

E%!$!y-Rel(!$o%=$p D$(&"(m

The entity relationship model is a generali/ation of primitive commercial systems$ which are

based on hierarchical and network approaches. The %21 relationship$ which is also known as

%ntity 1elationship is based on the theory of real world which consists of a set of basic objects$


36/69

which are called entities and relationships among these object. An entity eists as an object and

is distinguishable from other objects.

%ntity 1elationship 'iagram is popular data modeling tool. An %12'iagram can epress the

overall logical structure of a database graphically. An %12'iagram illustrates data at rest. #t gives

more detailed picture of the data stores$ independent of the processing. The %12'iagram shows

the pictorial representation of the system database. #t describes the 'istinguishable %ntity sets$

their attributes and relation established between the different entities. #t is detailed logical

representation of the data for an o%l$%e Mo+$le =opp$%& and user three main constructs2'ata

entities$ relationships and attributes. %1 'iagrammatic representation of the database design$ %1

'iagram is like blue print of database.

Fo" e(mple: account number 0@@3 at the #C#C# bank is an entity that uniuely identifies one

particular account.

;u$del$%e 1o" D"(/$%& E-R D$(&"(m:-

;hen gathering information # have to72

A. #dentify the entities in the system.

B. #dentify the attributes of each entity.

C. #dentify the relationship between the entities.

E%!$!y:

Any distinguishable person$ place$ thing$ event or concept about which information is kept or an

object which can be distinctly identified and distinguished and represented in a database or

anything about which we store information is called an E%!$!y2

Rel(!$o%=$p: -

A relationship is an “(o*$(!$o% (mo%& e%!$!$e” relation is the link between objects through

which a entity is related with other entity.

A!!"$+u!e:-


37/69

Attributes describe the entity to which they are associated. A particular instance of an

attribute is a value. #n other words attributes are the characteristics of an entity type. Attributes

can be classified as descriptors or identifiers. A descriptor describes a non2uniuely identify an

instance of an entity.

No!$1$*(!$o% 1o" E-R D$(&"(m:-

There is no standard for representing data objects in %21 diagram. %ach modeling

methodology uses its own notation. All notational style represents entities as rectangular

boes and relationship as lines connecting boes. %ach style uses a special set of symbols

to represent the cardinality of a connection. An entity is represented in %21 diagram as a

rectangular bo enclosing the entity type name.

Attribute names are enclosed in ellipses and attached to their entity type by straight lines.

T=e ym+ol ued 1o" !=e +($* E-R *o%!"u*! ("e


38/69

No!(!$o% Ue )ym+ol

L$%e 9inking

attributes to

entity sets to

relationship sets

Ell$pe 1epresenting

attributes

Re*!(%&le 1epresenting

entity set

Key:-

A key is a value which can always be used to uniuely identify an object instance. #t

becomes important to invent a method to distinguish entity and relationship. The differences

between entities must be epressed in terms of attributes.

)upe" Key:-

A (uper Ney is a set of one or more attributes which$ taken collectively$ allows us

to identify uniuely an entity in the entity set.

C(%d$d(!e Key:-

An attribute that uniuely identify a row is called Candidate Ney. Candidate key

is also referred to as (urrogate keys.


39/69


40/69

consumer of the data. A source or sink is typically outside the main system of study. The

')' should be carefully scrutini/ed to make sure that all the process in the physical

environment are shown in ')'.

#t should also ensure that none of data flow is actually carrying control information.

Fe(!u"e o1 DFD:-

D The eceptional simplicity of the ')' /ymology is one reason why data oriented

analysis techniues is the most widely used.

D The data flow diagram is a graphical tool that can be very valuable during the system

analysis.D The ')' depicts information flow without eplicit notation of control.,e.g. conditions of

loops-.

D The level @ data flow diagram should depict the software as a single bubble.

D Primary input=output files should be maintained.

D *ne bubble at a time should be refined.

There is a natural tendency to over complicate the ')'. This happens when we try to show too

many details early.


41/69

Lo/ le'el de$&%

The low level design documents for a project should provide a complete and detailed

specification of the design for the software that will be development in the project$ including the

LOW LEVEL

DESIGN


42/69

classes$ member and non2member function$ and associations between classes that are involved.

By the end of the low level design stage$ the code should beK all but writtenK.

The low level design document should contain a listing of the declarations of all the classes$ non2

member2functions$ and class member function that will be defined during the implementation

stage$ along with the associations between those classes and any other details of those classes

,such as member variables- that are firmly determined by the low level design stage. The low

level design document should also describe the classes$ function signatures$ associations$ and any

other appropriate plan defined in the project+s reuirement document. &ore importantly$ each

project+s low level design document should provide a narrative describing ,and comments in

your declaration and definition files should point out- how the high level design is mapped into

its detailed low2level design$ which is just a step away from implementation itself. This should

be an %nglish description of how you converted the technical diagram ,and tet description

found in your high level design into appropriate class and function declarations in your low level

design. Lour should be especially careful to eplain how the class roles and their methods were

combined in your low level design. And any change that you decided to make in combining and

refining them.

Modul( "(!$o%:


43/69

A system is considered modular if a consist of discreet component show that each

component can be implemented separately$ and a change to one component has minimal

impact on other components.

• %ach function in each abstraction has a single$ well defined purpose.• %ach function manipulates no more than one major data structure.

• )unction share global data selectively .it easy to identify all routines that share a

major data structure.

• )unction that manipulates instances of abstract data types are encapsulated with

the data structure be in manipulated.

)!"u*!u"e *=("!:

The structure chart is one the most commonly used methods for system design. (tructures

chats are used during architectural design to document hierarchical structure$ parameters

and inter connection in a system.


44/69


45/69

The goal of the coding or programming phase is to translate the design of the system

produced during the design phase into code in a given programming language which can

be eecuted by a computer$ and which performs the computation specified by the design.

)or a given design$ the aim is to implement the design in the best possible manner.

The coding phase affects both testing and maintenance profoundly. As we saw earlier$ the

time spent in coding is a small percentage of the total software cost$ while testing and

maintenance consume the major percentage. Thus it should be clear that the goal during

coding should not be to reduce the implementation cost$ but the goal should be to

reduce the cost of later phases$ even if it means that the cost of this phase has to be

increase. #n other words$ the goal during this phase is not simplify the job of the

programmer. 1ather the goal should be to simplify the job of the tester and the

maintainer.

This distinction is important$ as most programmers are individualistic$ and are mostly

concerned about how to finish their job uickly$ without keeping the later phases in

mind. 'uring implementation it should be kept in mind that the programs should not be

constructed so that they are easy to write but$ that they are easy to read and understand.

There are many different criteria for judging a program$ including readability$ si/e of the

program$ eecution time$ and reuired memory.

'ifferent programmers were reuired to implement a program$ and were given different

goals. #t was found that the programs written by different programmers were very

different$ and each tended to satisfy its goal. for our purposes ease of understanding and

modification should be the basic goals of the programming activity. This means that

simplicity and clarity are desirable$ while cleverness and compleity are undesirable.

P"o&"(mm$%& P"(*!$*e


46/69

The primary goal of the coding phase is to translate the given detailed design into source

code in a given programming language$ such that code is simple$ easy to test$ and easy

to understand and modify. (implicity and clarity are the properties a programmer should

strive for in the programs.

Top-Do/% (%d Bo!!om-Up:-

The design of a software system consist of a hierarchy of modules.

The main program invokes its subordinate modules$ which in turn invoke

their subordinate modules and so on.

#n a top down implementation$ the implementation starts from the top of the hierarchy$

and then proceeds to the lower levels. )irst the main module is implemented and then its

subordinates are implemented and then their subordinates and so on. #n a bottom up

implementation$ the process is the reverse. The development starts with implementing the

modules that are at the bottom of the hierarchy.

The implementation 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. #t is

most reasonable to have implementation proceed in a top2down manner if testing is being done

in a top2down manner. *n the other hand$ if bottom2up testing is planned then bottom2upimplementation should be preferred.

)!"u*!u"ed P"o&"(mm$%&:

(tructured programming is often regarded as &o !o-le programming. A program has a static

structure as well as a dynamic structure. The static structure is the structure of the tet

of the program which is usually just a linear organi/ation of statements of the program.

The dynamic structure of the program is the seuence in which the statements are

eecuted during the program eecution.

The goal of structured programming is to write a program such that its dynamic

structure is the same as its static structure. #n other words$ the program should be

written in a manner such that during eecution its control flow is liberali/ed and follows


47/69

the linear organi/ation of the program tet. )or structured programming$ a statement is

not a simple assignment statement$ but could be a structured statement. The key property

is that the statement should have a single entry and single eit. That is during eecution$

the eecution of the statement should start from one defined point and the eecution

should terminate at a single defined point.

I%1o"m(!$o% H$d$%&:-

To reduce coupling between modules of a system it is best that different modules be

allowed to access and modify only those data items that are needed by them. The other

data items should be JhiddenK from such modules and the modules should not be allowed

to access these data items. 9anguage and operating system mechanisms should preferably

enforce this restriction. Thus modules are given access to data items on a Jneed to knowK

basis.

*ne form of information hiding that is supported by many modern programming

language is d(!( (+!"(*!$o%. The advantage of this form of data abstraction is that the

data is entirely in the control of the module in which the data is encapsulated.

P"o&"(mm$%& )!yle:-

#t is impossible to provide an ehaustive list of what to do and what not to do in order

to produce a simple and readable code. Being able to do this will amount to providing

an algorithm for writing good code. !ere we will list some general rules which are

usually applicable2

5? N(me:-

&ost variables in a program reflect some entity in the problem domain$

and the modules reflect some process. ?ariable names should be closely related to


48/69

the entity they represent and module names should reflect their activity. #t is bad

to choose cryptic names or totally unrelated names.

6? Co%!"ol *o%!"u*!:-

As discussed above it is desirable that as much as possible single entry$

single eit constructs should be used. #t is also desirable to use a few

standard control constructs rather than using a wide variety of constructs$ just

because they are available in the language.

7? ;o !o : - o to s should be used sparingly and in a disciplined manner. *nly when

the alternative to using go to s is more comple should the go to s be used. #n any

case alternatives must be thought of before finally using a go to. #f a go to must be

used forward transfers is more acceptable that a backward jump.

8? I%1o"m(!$o% H$d$%&:- #nformation hiding should be supported where possible. *nly

the access functions for the data structure should be made visible while hiding the

data structure behind these functions.

9? Ue" De1$%ed Type :- &odern languages allow the users to define types like the

enumerated type. ;hen such facilities are available$ they should be eploited where

applicable.

? Ne!$%&: -

The different control constructs$ particularly the if2then2else$ can be nested. #f the

nesting becomes too deep$ the programs become harder to understand. #n case of

deeply nested if2then2else$ it is often difficult to determine the if statement to

which a particular else clause is associated. ;here possible$ deep nesting should

be avoided even if it means a little inefficiency.

? Module )$@e:-


49/69

A programmer should carefully eamine any routine with very few statements or

with too many statements. 9arge modules often will not be functionally cohesive and

too small modules might be incurring unnecessary overhead. There can be no hard

and fast rule about module si/e and the guiding principle should be cohesion and

coupling.

? Module I%!e"1(*e:-

A module having a comple interface should be carefully eamined.

(uch modules might not be functionally cohesive and might be

implementing multiple functions. As a rule of thumb any module whose

interface has more than five parameters should be carefully eamined and

broken into multiple modules with a simpler interface if possible.

G? P"o&"(m L(you!:-

!ow the program is organi/ed and presented can have great effect on the

readability of programs. Proper indentation$ blank spaces$ and parenthesis should

be employed to enhance the readability of programs. Automated tools are

available to “p"e!!y p"$%!” a program$ but it is good practice to have a

clear layout of program.

5? )$de e11o"!:-

;hen a module is invoked$ it sometimes has side effects of modifying the

program state beyond the modification of parameters listed in the module interface

definition$ for eample$ modifying global variables. (uch side effects should be

avoided where possible$ and if a module has side effects$ they should be properly

documented.

Ro+u!%e:- Program is robust if it does something planned even for eceptional

condition. A program might encounter eceptional conditions in such forms


50/69

as incorrect input$ the incorrect value of some variable and overflow. A

program should try to handle such situations. #n general a program should

check for validity of inputs$ where possible$ and should check for possible

overflow of the data structures. #f such situations do arise$ the program

should not just JcrashK or Jcore jumpK $ but should produce some

meaningful message and eit gracefully.


51/69

SCREEN

SHOT


52/69


53/69


54/69


55/69


56/69


57/69

TESTING


58/69

Te!$%&:-

The code is tested at various levels in software testing. Enit$ system and user acceptance testing

are often performed. This is a grey area as many different opinions eist as to what the stages of

testing are and how much$ if any iteration occurs. #teration is not generally part of the waterfall

model$ but usually some occur at this stage. #n the testing the whole system is test one by one

)ollowing are the types of testing7

D Defect testing the failed scenarios$ including defect tracking

D Path testing

D 'ata set testing

D Enit testing

D (ystem testing

D #ntegration testing

D Black2bo testing

D ;hite2bo testing

D 1egression testing

D Automation testing

D Eser acceptance testing

D (oftware performance testing

)y!em Te!$%&:-

#t involves two kinds of activities7 integration testing and acceptance testing developing

strategy for integration the components of a software system in to a complete system


59/69

reuires functioning of the whole system and careful planning so that modules are

available for integration when needed.

Acceptance testing involves planning and eecution of various types of tests in order to

demonstrate that implemented software system satisfies the reuirement document.

I%!e&"(!$o% !e!$%&:-

#t is a systematic techniue for testing the programmed structure while at

the same time conducting test to uncover errors associated with interfacing. The

objective is to play unit tested modules and build a programmed structure that has

been dedicated by design. Bottom2up integration was used in developing.

Te!$%& me*=(%$m:-

(oftware testing is the most important phase of any software development

life cycle. #t is the testing part$ which validates the software and check whether

the software is working as desired or not. The major purpose of testing is to

retrieval bugs in the software. #n testing software design is eecuted with various

test inputs for which the test programmer knows result in advance. The departure

of the programmed output from the known results confirms that the software

contains error.

Testing is divided into following phases72

D The module interface was tested to assume that information properly float into

and out of the program unit test.

D The local data structure was eamined to assume that data stored temporally

maintain their integrity during all steps in an algorithm eecution.

D Boundary condition were tested to assume that module operated properly at

boundaries establish to limit or restrict processing.


60/69


61/69

Te! )*"$p!:-

The development team has vision of what they want$ they want to create$ a

commitment to getting as close to the dream as they can$ and recognition to that they+ll

have to flash out details by trial and error. By the time they have worked out the final

detail of one aspect of the product$ they have working version that one or two key people

understand fully. That version is the JspecificationK. #t is not engraved in stone7 it will be

reviewed and polished later$ to achieve consistency with other parts of the system. &uch

of polished may be at a suggestion of a tester.

'esirable features are freuently dropped because there is no time to implement then code

rewrites are also set aside$ even if they are needed to bring a fragile first working version to a

level a programmer considers professional. A conscientious programmer might take the initiative

and do the job anyway$ Jon the slyK late in the project: he may drop a significant change into the

package without warning. These efforts go beyond the call of duty and the @2hour week. They

may improve the product tremendously or destabili/e it badly$ probably both for a time.

;hatever the result$ people take personal initiative to improve the product. These are always late

changes$ the goal is to with then2they are needed as painlessly as possible. The goal is not to

create administrative system to inhibit them. #f we can+t keep up with then as tester$ we have a problem. But the solution won+t come from complaining about or in trying to stop them.

P=(e $% Te!$%&:-

Testing was done in following phases7

• )irst the live database was portable form previous database version to visual studio 6.@

for testing but later real implementation has to be done.

• And on client machine setup for particular module was installed.

• And also &( Access was installed and et service name was created for connecting the

database on T server.


62/69

• Then the module which consists of data entry form$ process form$ reports enuiries were

tested by entering the real data which was taken from the respective department.

TE)T INFORMATION FLO:-

A strategy for software testing may also be viewed in the contet of the

spiral. Enit testing begins at the vorte of the spiral and$ concentrates on each

unit$ component of the software as implemented in source code. Testing

progresses moving outward along the spiral to integration testing$ where the focus

is on designed the construction of the software architecture. Taking another turn

outward on spiral$ we encounter validation testing$ where reuirements

established as part of software reuirements analysis are validated against the

software that has been constructed. )inally$ we arrive at system testing$ where the

software and other system elements are tested as a whole. To test computer

software$ we spiral out along stream lines that broaden the scope of testing with

each turn.

Considering the process from a procedural point of view$ testing within the contet of software

engineering is actually a series of four steps that are implemented seuentially. The steps are

shown in )igure. #nitially$ tests focus on each component individually$ ensuring that it functions

properly as unit. !ence$ the name unit testing. Enit testing makes heavy use of white2bo testing

techniues$ eercising specific paths in module+s control structure to ensure complete coverage

and maimum error detection.


63/69

IMPLEMENTATION

&MAINTENANCE


64/69

Impleme%!(!$o%

#mplementation is the carrying out$ eecution$ or practice of a plan$ a method$ or any design for

doing something. As such$ implementation is the action that must follow any preliminary

thinking in order for something to actually happen. #n an information technology contet$implementation encompasses all the processes involved in getting new software or hardware

operating properly in its environment$ including installation$ configuration$ running$ testing$ and

making necessary changes. The word deployment is sometimes used to mean the same thing.

The #mplementation Phase is the final phase of the ('9C and it involves the actual construction

and installation of a system. This phase also includes the maintenance of the system and any

future updates or epansion of the system. ;ith the database project eample$ the following

activities would be common7

There are several activities involved which implementing a new project they are7

• %nd user training.

• %nd user education.

• Training on the application software.

• (ystem design.

• Parallel run and to new system.

• Post implementation review.

E%d ue" !"($%$%&:

The successful implementation of the new system will purely upon the involvement of

the officers working in that department. The officers will be imparted the necessary training on

the new technology.

E%d ue" edu*(!$o%: -


65/69

The education of the end user start after the implementation and testing is over.

;hen the system is found to be more difficult to understand and comple more

effort is put to education the end used to make them aware of the system$ giving

then lectures about the new system and providing them necessary documents and

materials about how the system can do this.

T"($%$%& o1 (ppl$*(!$o% o1!/("e: -

After providing the necessary basic training on the computer awareness.

The users will have to be training upon the new system such as the screen flow

and screen design type of help on the screen$ type of error while entering the data$

the corresponding validation check at each entry and the way to correct the data

entered. #t should then cover information needed by the specific user or group to

use the system.

Po! $mpleme%!(!$o% '$e/: 2

The department is planning a method to know the states of the past

implementation process. )or that regular meeting will be arranged by the concerned

officers about the implementation problem and success.

M($%!e%(%*e


66/69

(oftware maintenance is the last phase in the software engineering process that eliminates

error in the working system during its work span and to tune the system to any variation

in its working environment. The system reuire maintenance as there may be changes and

reuirements in the organi/ational needs$ government policies$ hardware and software

environment etc. often small system deficiencies are found as a system is brought into

operation and changes are made to remove then. (ystem reuirements may be revised as

a result of system usage or changing operational needs. Perhaps oversight that occurred

during the development process needed to be corrected. *ften the maintenance need

arises to capture additional data for storage in a database or in transaction$ files or

perhaps it may be necessary to add error detection features to prevent system users from

in adversely taking an unwanted action.

&aintenance of the system after it is installed is concerned with an additional factor in hardware.

*nce the system is delivered and installed there is a brief warranty period during which time the

vector is responsible for maintenance. This is typically a I@2day period after that time the

purchaser has the option of acuiring maintenance from various sources. &aintenance source

ecepting vendor is also available from companies speciali/ing in providing the service called

third party maintenance companies. )ollowing table summari/ed the broad classes of

maintenance found in development of information systems72


67/69

BIBLIO;RAPH<

REFRENCE

C(!e&o"y A*!$'$!y

5.Corrective debugging

6. Adaptive 'ata and to hardware and

software$ change in the eternal

environment.

7. Preference documentation

recording of computational

efficiency$ user recommendations for

new capabilities.

8. Preventive and adjusting the

euipment to prevent breakdowns$

future maintainability reliability

enhancement$ recovering design

information improves the overall

uantity.

%mergency fier$ routing.

Accommodation of changes.

Eser enhancement$ improved.

1outine service of cleaning.


68/69

BIBLIO;RAPH< REFERENCE

;ith tremendous advances in software technology$ it is very essential for software to be up to

date and user interactive keeping this fact in view$ # have tried my best to keep it to such level as

of today+s. (o$ to make it to this level$ # had to consult many books and media. These are the list

of books and media$ # have consulted72

BOOK):-

J*ffice 3@@@K by (AMAL (A


69/69

///2/7*=ool2*om

http://www.w3school.com/http://www.w3school.com/

Sps Projectn Report

Documents

Transcript of Sps Projectn Report