Copy of the Crackers

8/8/2019 Copy of the Crackers

1/55


2/55


3/55


4/55


5/55


6/55


7/55


8/55


9/55

11) T rack Support T ransactions: Maintenance of transactions related to the

services provided to the customer in the form of support.

12) View: In this module, customer view about insurance policies and agents

contact information for choosing policies and respective agents. 13 ) H elp: In this module, two types of help is provided by Administrator, First

is for customer in order to provide online help related to the system and

second is for agent to provide online training modules.

2.0 6 ) User C haracteristics: Every user must be comfortable while working withcomputer and net browsing. He must have basic knowledge of English too.

2.0 7 ) C onstraints:

y GUI is only in English.y Login and password is used for identification of customer and there is

general information for guest regarding policies provided by company.y This system works under single server.y Limited to HTTP/HTTPS.

2.0 8 ) Use- C ase M odel Survey:

US E C AS E D IA G RA M

1. Administrator: Responsible for managing system users i.e agents &customer, also control the whole insurance system.


10/55

(a) Login : To do over work on insurance system then first will login to theSystem with required information like id, password etc.

(b) P rofile management : The Administrator will manage all agents &

Customers information & detail in the database.

(c) Add /Update agents : The Administrators can add some new agents

and update their information. While updating, administrator apply

changes in agents information like agents name, add. etc.

Administrator can also add new agents.

(d) G enerating Various Reports: Administrator generate various reports

which is related to the system. Such as regarding insurance policies etc.

(e) Account: The Administrator will manage account of all agents andcustomers .He is Responsible for checking the account of different type

of policies of customer and agents .

(f) Adding new policy: Administrators can add new policies, news notice

launched by insurance company. First admin check the policy wether it

is benifitial for his system or not and if it is profitable then it allows it to

be add into system. All policies will be updated by the administrator.

(g) View All D etails: View the agent details and details of customers.(h) On Line H elp : It is provided only to agent and customer . For

customer help is related to his insurance policy which he choose andsome other helps, but for agents on line training module is given byadmin.

2. Agents: Responsible for managing customer details, data transaction,

managing policy service, catalogs and grouping the related customers.

(a) Login: To do over work on insurance system then agent will first

login to the System with required information like id, password etc.


11/55

(b) View All D etails: View the customer details, payment details,

purchase details, daily service transaction details. Manage Groups:

Categorize the customers into local groups according to some

criteria.(c) C heck claims: In this phase the agent ckecks the claims of the

customer and undertake process accordingly.

(d) Send mail, alerts and News: In this phase the agent sends alert

mails to the customer regarding premium date (in advance) and send

other news related to the Insurance policies.

(e) H andle C omplains: In this phase the agent handles the complaints

received from the customers.

(f) P remium C alculation: Here agent calculates the Premium of

customers.

(g) Receive P remium: Here agent will receive premium amount from

the customers and will send detail to the administrator.

(h) Log Out: Now agent will log out3 . C ustomer: The customer is also one of the essential part of this system.

The customer is provided with policies and it also selects particular agent

for particular policies.

(a) W eb Registration: Here customer get registered with the company by

filling the registration form.

(b) Login: Customer logged in to perform related operations by entering

id and passwords.(c) Select P olicy: Here customer selects policy and fills respected policies

form and choose the agent accordingly.


12/55

(d) C laims Reporting: Here customer claims for his/her premium amount

accordingly to policy.

(e) D eposit P remium: Customer deposits premium accordingly and

within time limit.(f) W ithdraw P remium: Customer can withdraw policy after maturity

and even before maturity, and will be paid accordingly.

(g) Log Out: Now customer will log out.

2.09) Architecture diagram:RoleRole_UIUser_UILog_UIPermission_UITask_UIRoleUser LogTask Permission

Receivable_UI ReceivableCustomer_UIPurchase_UIProduct_UIService_UISLA_UICustomer PurchaseProductServiceSLAServiceTransaction_UIServiceTransactionGroup_UI GroupLog


13/55

PermissionTask ReceivableSLACustomer SalesProductServiceService TransactionGroupApplication Layer Business Layer Data Layer User 2.09) Architecture diagram:RoleRole_UI

User_UILog_UIPermission_UITask_UIRoleUser LogTask PermissionReceivable_UI ReceivableCustomer_UIPurchase_UIProduct_UIService_UISLA_UICustomer PurchaseProductService

SLAServiceTransaction_UIServiceTransactionGroup_UI GroupLog


14/55

PermissionTask ReceivableSLACustomer SalesProductServiceService TransactionGroupApplication Layer Business Layer Data Layer User

112.10) Database design:System_RoleRole_IDRole_NameSystem_Role_Task Role_IDTask_IDSystem_Task Task_IDTask_NameSystem User User_IDLogin_namePassword_valueFirst_NameLast_NameE-mailModified

CreatedISASalesManager AccountManager Support


15/55

Manager HasSystem_LogUser_IDActivityDate/TimeSystem_PermissionPermission_IDPermission_NameGroup_User Group_IDUser_IDGroup_Customer Group_ID

Customer_IDGroupGroup_IDGroup_NameGroup_DescriptionMakesSystem_task_PermissionTask_IDPermission_ID2.10) Database design:System_RoleRole_IDRole_NameSystem_Role_Task Role_IDTask_IDSystem_Task Task_IDTask_Name

System User User_IDLogin_namePassword_valueFirst_NameLast_NameE-mail


16/55

ModifiedCreatedISASalesManager AccountManager SupportManager HasSystem_LogUser_IDActivityDate/Time

System_PermissionPermission_IDPermission_NameGroup_User Group_IDUser_IDGroup_Customer Group_IDCustomer_IDGroupGroup_IDGroup_NameGroup_DescriptionMakesSystem_task_PermissionTask_IDPermission_ID

12Customer Customer_IDLogin_namePasswordCompany_NamePhone


17/55


18/55

Launching_DateSalesBill_NoCustomer_IDProduct_IDPurchase_DatePurchase_TimeQty_SoldSupply_DateTotal_AmountAmount_LeftServiceService_IDDescription

PriceDurationSupport_FacilitySLASLA_IDCustomer_IDProduct_IDSLA_NameLeft_amountTotal_CastSLA_DescriptionSLA_RuleResolution_TimeDaysTimeMinutesTerms_&_ConditionsAmount_leftSLA_Service

SLA_IDService_IDSupport_TransactionSLA_IDContact_IDMode_of_TransactionSubject


19/55

DateTimeTransaction_DetailService_Manager Support_Manager Responder Initiator ReceivablesReceivable_noReceivable_for DateType_of_PaymentMode_of_PaymentCheck#

Check_Bank Check_Issue_dateCheck_Expiry_dateCheck_AmountDD#DD_Bank DD_IssueDD_Expiry_DateDD_AmountCash_AmountCard#Bank AmountCustomer Customer_IDLogin_namePasswordCompany_NamePhone

ExtensionFaxAddressCityStateCountryZip Code


20/55

WebsiteE-mailHaveContact _PersonContact_IDContact_NamePerson_IDDepartment_NameSalutationPhoneExtensionMobileFaxAddress

CityStateCountryZip_CodeE-mailMessanger_IDReference_byProductProduct_IDDescriptionProfit%Unit_MeasureQty_in_HandReoreder_levelSale_PriceCost_PriceImageGuarantyStatus

Launching_DateSalesBill_NoCustomer_IDProduct_IDPurchase_DatePurchase_Time


21/55

Qty_SoldSupply_DateTotal_AmountAmount_LeftServiceService_IDDescriptionPriceDurationSupport_FacilitySLASLA_IDCustomer_IDProduct_ID

SLA_NameLeft_amountTotal_CastSLA_DescriptionSLA_RuleResolution_TimeDaysTimeMinutesTerms_&_ConditionsAmount_leftSLA_ServiceSLA_IDService_IDSupport_TransactionSLA_IDContact_IDMode_of_TransactionSubject

DateTimeTransaction_DetailService_Manager Support_Manager Responder Initiator


22/55

ReceivablesReceivable_noReceivable_for DateType_of_PaymentMode_of_PaymentCheck#Check_Bank Check_Issue_dateCheck_Expiry_dateCheck_AmountDD#DD_Bank DD_Issue

DD_Expiry_DateDD_AmountCash_AmountCard#Bank Amount

13Sales Manager Customer SLA SalesProductServiceContact_PersonAccount Manager Sales SLAGroup Group_Customer Group_UserReceivableGroupGroup_Customer

Group_User Support Manager Group_User Group_Customer Group_User Support_TransactionSLASales Manager Customer SLA SalesProductService


23/55

Contact_PersonAccount Manager Sales SLAGroup Group_Customer Group_UserReceivableGroupGroup_Customer Group_User Support Manager Group_User Group_Customer Group_User Support_TransactionSLA

2.11) Assumptions and Dependencies:

? The details related to the product, customer, payment and service transaction provided manually.? Administrator is created in the system already.? Roles and tasks are predefined.

3) Specific Requirements:

3.1) Use-Case Reports:

i) Administrator: Responsible for managing system users, viewing logs andmanaging standard groupsof the system.

?Manage System Users: The Administrator will create different roles. The systemusers will

be created and will be assigned with the different roles. More than one task and permissions

can be granted or revoked from the system users.

?View Logs: Responsible for checking the logs of different system user for auditing andmaintaining the integrity of the system.


24/55

?Manage Standard Groups: Standard groups will be created and updated by theadministrator, which will be visible to all the system users.

?View All Details:View the customer details, payment details, purchase details,daily servicetransaction details.

Manage System Users:

Manage System UsersView System UsersCreate System Users

Update details of Users

Name of use case: View System UsersDescription: View the list of system users in a role and view the details of roles, tasks and permissions assigned to a system user.

Preconditions:

? Administrator is already logged in.? System users have already been created and assigned some roles, tasks and

permissions.

Normal flow of events:

The system user or a role will be selected.

Query will be submitted.


25/55

Relevant output will be displayed (If system user is selected then roles, tasks and permissions assigned to one will be displayed and if role is selected then list of systemusers assigned to that role will be displayed).Alternate flow of events:None.

Post Condition: None.

Ask for selecting Roleor System User Details of roles, tasks and

permissions of selected user List of system users which are

assigned to the selected role[System User][ Role ]

Name of use case: Create System UsersDescription: To create system users (Giving them a login name, passwordand assign roles, tasks and permissions to them).Preconditions: Administrator is already logged in.


New Login name, password, details, roles, tasks and permissions will beentered.

Save the details.Alternate flow of events:

A message appears for duplicate login name.

The administrator has to fill the details again.Post condition: A login id is generated with its details.Enter login name, password, details, rolename, check the tasks and permissions[ Duplicate Login Name ]User successfully


26/55

created

Name of use case: Update details of UsersDescription: To update the details of system users (assigning or revoking roles,tasks and

permissions).

Preconditions:

? Administrator is already logged in.? System Users have already been created.


Select the user name.

Assign or Revoke the roles, tasks and permissions.

Post Condition: None

Ask for selecting thesystem user Updations in role, tasksand permissions

Name of use case: View logsDescription: To view the activities (logs) of the system users.Precondition:? Administrator is already logged in.? System Users have already been created.


? Select user name.? Select date.Post Condition: None


27/55

Select user nameSelect DateLogs of system user of selected dates

ii) Sales Manager: Responsible for managing customer details, sales transaction,managing products,service catalogs and grouping the related customers.

Manage customers: Record details of new customers, update and view its details.

Create Sales Transaction: Record details of product sold, customer id, terms andconditions and service level agreements.

Manage product/service catalogue:Creation and updation of product/servicedetails.MANAGE CUSTOMERS

Add new contact persons

Manage customers

Add customers

Update C ustomers


28/55

View its details

Add a new contact specificneed

Name of use case: Add CustomersDescription: To create the details of the new customer.Preconditions: Sales manager is already logged in.


The details of the customer entered.

Save the details.

Creation of the customer will be entered in the log.Alternate flow of events:

A message appears for unfilled fields.

The sales manager has to fill the details again.Post condition: A customer id is generated.

Name of the use case: Add a new contact specific need.Description: To meet the specific needs of the customer, the sales manager can

add a newcustom field for the customer.Precondition: Sales manager is already logged in.


Select a customer.


29/55

Enter the specific need of the customer.

Save the new data.

Creation of the contact specific need will be entered in the log.Alternate flow of events:

If the customer is not present, create the customer.Post condition: None.

Name of the use case: Add new contact persons.Description: To create the details of a new contact person of the selected

customer.Precondition: Sales manager is already logged in.


Select customer.

Enter details of contact person.

Save new data.

Updation of the contact person will be entered in the log.Alternate flow of events:

If customer id not present create customer.Post condition: None

Name of use case: Update customers.Description: Any updation in the details of the customer can be made.Precondition: Sales manager is already logged in.


Select a customer.


30/55

Customers data updated.

Save the changes.

Updation of the customer will be entered in the log.Alternate flow of events:None.Post condition: None.Ask for acustomer Display the detailsof the customer select customer Store changesCustomer's data updated

Add updationinformation in the log

Name of the use case: View customer details.Description: View the personal details of the selected customer.Precondition: Sales manager is already logged in.


Select customer.

The details of customer viewed.Alternate flow of events: NonePost condition: None.Ask for customer Display customer

personal detailsSelect customer CREATE SALES TRANSACTION


31/55

Add purchase details

Manage purchase details

Update purchase

View purchase details

Create sales Transaction

Create a SLA

Manage Service Level

View a SLA

Agreements

Update SLA


32/55

Name of the use case: Add purchase details.Description: Store the details of the product sold, customer id and supply details.Precondition: Sales Manager is already logged in. The customer and the productare already

present.


Select a customer.

Select a product.

Enter purchase details.

Save new data.

Creation of the purchase details will be entered in the log.Alternate flow of events:

If the customer is not present, create the customer.

If the product doesnt exist, create the customer.Post condition: Product id is generated.Ask for detailsof purchaseAsk for customer Select customer Create

customer invalidAsk for

productValidSelect productCreate


33/55

productStore newdataPurchase details enteredinvalidValidStore add informationin the logs

Name of the use case: Update purchase.Description: Any changes in product details can be made.Precondition: Sales manager is already logged in. The product is already present.


Select product.

Edit the data where needed.

Save changes.

Updation in purchase details will be entered in the log.Alternate flow of events:

If product doesnt exist, create product.Post condition: None.Store updateinformation in the logsAsk for customer Select customer

Createcustomer invalidAsk for

productValidSelect product


34/55

Create productAsk for a datePurchasedetails shownSelect dateinvalidValidStorechangesUpdate purchase details

Name of the use case: View purchase details.Description: View the details of the product purchased by the selected customer.

Precondition: Sales manager is already logged in. The product and the customer are already

present.


Select product.

Select customer.

The purchase details are shown to the sales manager.Alternate flow of events:

If the customer doesnt exist, create customer.

If the product is not present, create product.Post condition: None.Createcustomer Ask for customer Select customer


35/55

invalidAsk for


productAsk for a datePurchasedetails ShownSelect dateinvalidValid

Name of the use case: Create a service level agreement.Description: Store the details of the services provided to a customer, duration of the servicesand details of the terms and conditions

Precondition: Sales manager is already logged in. The product, customer and theservices to be

provided are already present.


Select product.

Select customer.

Select service/s

Enter details of the service level agreements.

Save the new data.

Creation of the SLA will be entered in the log.Alternate flow of events:


36/55


If the product is not present, create product.

If the service is not present, create service.Post condition: SLA id is created.Ask for SLAdetailsAsk for customer Select customer Create

customer invalidAsk for


productAsk fo r one or more servicesSelect service/sinvalidValidStore newdataSLA entries enteredStore add informationin the logs

Name of the use case: Update service level agreement.Description: To edit the details of the SLA made with the customer.Precondition: Sales manager is already logged in. The product, customer and theservices to be



37/55


Select product.

Select customer.

Select date.

Edit the details.

Save the changes.

Updations of the SLA will be entered in the log.Alternate flow of events:


If the product is not present, create product.Post condition: None.

Name of the use case: View service level agreement.Description: To see the details of the agreement made with the selected customer.Precondition: Sales manager is already logged in. The product, customer and theservices to be



Select product.

Select customer.

Select date.


38/55

The details of the SLA are shown to the sales manager.Alternate flow of events:


If the product is not present, create product.Post condition: None.Ask for customer Select customer Createcustomer invalid

Ask for productValidSelect productCreate

productAsk for a dateSLA detailsShownSelect dateinvalidValid

MANAGE GROUPS

Create a groupManage groups

Group the related customers

Name of the use case: Create a groupDescription: A new group is created.


39/55

Precondition: Sales manager is already logged in. Normal flow of events:

Enter a group name.

Enter its description.

Save the new data.

Creation of the group will be entered in the log.Alternate flow of events:Post condition: None.

Ask fo r group nameAsk for groupdescriptionGroup name enteredStore newdataGroup description enteredStore addinformation in log

Name of the use case: Group the related customer.Description: The related customers are added in the selected group.Precondition: Group name and customer should be already present.


Select group name.

Select the customer.

Add the customers to the selected group.

Grouping information will be added in the log.


40/55

Alternate flow of events:

If the group doesnt exists, create a group name

If the customer is not present, create the customer.Post condition: None.Ask for agroup nameAsk for customer listselect groupAdd customers tothe selected groupSelect customer

Add aditioninformation in the log

Name of the use case: View the customers in the selected group.Description: The customers added in a group can be viewed.Precondition: Group name and customer should be already present.


Select group name.

The customers in the selected group is shown.Alternate flow of events:

If the group doesnt exists, create a group name

If the customer is not present, create the customer.Post condition: None.

Ask for group nameDisplay list of customersin the selected groupSelect group nameAsk for


41/55

group nameDisplay list of customersin the selected groupSelect group nameMANAGE PRODUCT/ SERVICE CATALOGUE

Create product/servicedetails

Manage product/service Update product/servicecatalogue

details

View product/service details

Name of the use case: Create product/service catalogue.Description: The product and service details are maintained in the form of cataloguePrecondition: The Sales Manager should be already logged in.


Enter the product/service details.

Save the new data.

Creation of the product/service will be entered in the log.Alternate flow of events:None.Post condition: None.


42/55

Ask for new product dataStore newdataUpdate View Product details entered[update ok]Displayerror [system error]Displayconflict[Duplicate product found]Creation informationstored in logs

Ask for new product dataStore newdataUpdate View Product details entered[update ok]Displayerror [system error]Displayconflict[Duplicate product found]Creation informationstored in logsUpdate Vie wAsk for newservice dataS tore newdat a

Service details entered[update ok]Displayerror [system error]Displayconflict


43/55

[D uplicate product found]C reation informationstored in log s

Name of the use case: Update the product/service details.Description: Updating in the details of the product/service are made.Precondition: The Sales Manager should be already logged in. The product should

be already present.


Select a product/service.

Edit the details.

Save the changed data.

Updation of the product/service will be entered in the log.


If the product/service doesnt exist then create product/service.Post condition: None.A sk fo r ase rviceD isp la y the de ta ilso f the se rvicese lect se rviceS to re changes

se rvice de ta ils update dAdd upda tioninfo rm a tion in the lo gAsk for a

productD isplay the detailsof the product


44/55

select productStore changes

product details updatedAdd updationinformation in the log

Name of the use case: View product/service details.Description: The product quantity, price, service details are displayed.Precondition: The Sales Manager should be already logged in. The product should

be already present.


Select product/service.

The catalogue of product/service is shown.


If the product/service doesnt exist then create product/service.Post condition: None.Ask for

productDisplay list of customersfor the selected productSelect productiii) Account Manager:Description: Manage all the payment details (of the product or services purchased). Group the customer according to

some criteria.? Manage Payment Transaction:Store all the payment transactions made by thecustomer and update the payment information.? View All Details: View the customer details, payment details, purchase details,daily servicetransaction details.


45/55

? Manage Groups: Categorize the customers into local groups according to somecriteria.

Manage Payment Transaction:

Accountmanager Manage payment transactiondetailsManage groupsView HistoryAdd payment transaction

detailsEdit the payment transactiondetailsCreate a groupAdd customer to groupUpdate the account of customer {or}{or}{or}{or}

Name of the use case: Add payment transaction details

Description: All the payment transaction details are entered.Pre condition: Account manager has logged in.


? Select the customer.? Select the product .? Select the bill number.


46/55

? Enter the details of receivables.? Save the receivables details.? Update the account of the customer.? Entry of this adding details event has been logged .

Alternate flow of event:

?If the receivables details will left to fill then system ask for refilling all the blank

details thensave the details and update the account of the customer.

Post condition: None.

Ask for theReceivablesStore theReceivablesReceivables enteredD isplayerror [Found error]Update account of customer [submission OK]

Name of the use case: Edit the payment transaction details:Description: Previously entered payment transaction details are updated.

Normal flow of event:?Select the customer.

?Select the product.


47/55

?Select the receipt number.

?Select the payment transaction number.

?Make the changes.

?Save the new details.

?Update the account of the customer.

?Entry of this editing event has been logged.

Post condition : None.

Ask for theBill number Ask for theBill number Bill number entered[Bill number found][Bill number not found]Editing done[Submission ok][Error found]D isplay filled form

of receivablesD isplayerror Storeupdated formD isplayError


48/55

Update account of customer iv) Support Manager: Responsible for entering details of daily servicetransactions withcustomer. He can view customer's personal, official, payment details. He can viewhistory of allthe customers, edit the customer transactions and can group the related customer.

?Manage Service Transactions:Record and edit the details of the daily transactionsof thecustomer for a service.

?

View All Details:View the customer details, payment details, purchase details,daily servicetransaction details.

?Manage Groups: Categorize the customers into local groups according to somecriteria.

Manage Service Transaction

Add ServiceTransaction

Manage Service

Update ServiceTransaction

Transaction


49/55

Edit ServiceTransaction

Name of use case : Add Service TransactionDescription : To add new transaction with a customer.

Normal flow of event :

Select the customer or enter name of responder

Select the contact person

Select SLA No

Enter the mode of transactionMode of transaction may be

e-mail

chats

service calls

meetings

Enter date and time

Enter subject of transaction

Feedback

Discussion on service provided for a product

Enter the name of initiator

Enter / Select details in transaction


50/55

Enter name of service provider

Save this transaction

Add transaction entry is made into LogAlternate flow of events:

Sales Manager will get a notification if customer/contact person does notexist in the system.

Ask for customer

customer entered Notify to salesmanager [ customer not exist in system ]Ask for cotact

personcontact enteredAsk for SLAAsk for subject, date , time, details intransaction, service man, support manager SLA enteredStore newdataAll require fields are enetredRecord addtransaction in logAsk for customer customer entered

Notify to salesmanager [ customer not exist in system ]Ask for cotact

personcontact enteredAsk for SLA


51/55

Ask for subject, date , time, details intransaction, service man, support manager SLA enteredStore newdataAll require fields are enetredRecord addtransaction in log

Name of use case : Edit transactionDescription: To edit the customer transaction.

Normal flow of event :

Select customer

Select contact person

Select SLA no

Make changes in transaction

Update the transactionAsk for C ustomer A sk for contactCustomer entered

conatct entered

A sk for SLA

SLA enterd

D isplaytransactionEdit thetransactionStore updated


52/55

transactionReco rd editentery into log

Name of use case : View history of customer Description : Support manager can view history of customers according to manycriteria, like

Customer name

Contact person

Product/ Service

Date

Time

Transaction mode

e-mail

chat

service calls

meetings

Subject

Feedback

Discussion of product/service

Name of the service provider

Name of support manager


53/55

Normal flow of events :

Select a criteria stated above

History will be visible to support manager

Support manager can delete transactionPost condition: Activities are registered in Log.Assumptions: Use cases Manage customer, Create sales transaction, Manage

product/ servicecatalog has been created.

Ask for customer Ask for customer Select transactions accordingto SLAAsk for SLACustomer enteredSLA enteredDIsplaytransactionRecord viewentery in LogAsk for date/ time/ subject/ mode of transaction/ service provider/ support manager Select transaction fromsupport transaction

DisplaytransactionRecord viewentryinto Log

Ask for service


54/55

Ask for SLAService enteredSelectcustomer SLA enteredSelect transaction fromsupport TransactionDisplaytransactionRecord viewentry in to LogAsk for customer Customer entered

Ask for cotactASK fo r SL AContact entere dSelect transaction fromsupport transactionDisplaytransactionRecord viewentry in to Log

3.2) Supplementary Requirements:

Have hours of operation that are 24 x 7 - Because system can be an automated process, so it can stay open for 24 hours a day. If the base is now the entire world,

staying open 24 hours a day becomes critical. System is required to be available24X7 soUPS support must be on server site for at least 8 hours in case of power failure.Systemwill remain inaccessible to users at 2:00 to 4:00 am for backup and maintenance

purpose.


55/55

Reduce the cost of a sales transaction -To the extent that one can automate thesales process through this system, one can start to reduce the cost of that salestransaction. This is particularly true of mundane sales transactions where thecustomer knows what they want.

Make the existing Web site more dynamic in nature -Many early Webimplementations consisted of static HTML pages. This becomes very difficult tomanageif the number of pages gets too large. An effective system should be largelydynamictaking advantage of technology that automates this process rather than relying onmanual

processes. Application should serve dynamic user based customized web pages to

itsclients from server.

Tie the existing Web site into existing enterprise systems Any existing Web sitethat relies on the manual duplication of data from another system is one that can

beimproved. Most of the business data in the world today exists in enterprise serversthatcan be connected to the Web servers to make this process far more effective.

Provide good performance and the ability to scale the server The WebApplication Server should provide good performance and the ability to manage

performance with techniques, such as support for caching, clustering, and load balancing.

Providing session management capability -Web application developers should notspend valuable time worrying about how to maintain sessions within theapplication. TheWeb Application Server should provide these services.

Copy of the Crackers

Documents

Transcript of Copy of the Crackers