You　want　to　use　the　Web　to　let　Eternal　users　or　your　customers　look　at　corporate　information.　But　you　want　to　keep　installation　at　the　user　end(66)and　you　don't　want　just　anyone　to　get(67)your　databases.

That　may　be　where　an　application　server　enters　the　picture.　For　more　user　machine　independent,　these　t　software　packages,　typically　written　in　the(68)programming　language.

for　use　on　Windows　NT-based　systems,　act　as　go-betweens　linking　browser-equipped　　end　users　to　the　databases　that(69)the　information　they　need　to(70)。

(67)

(66)

(64)

(65)

(61)

(62)

The　approach　we　propose　is　a　system-oriented　methodology　for　knowledge　acquisition.　This　orientation　emphasizes　ongoing　documentation　throughout　each　cycle　and　technique　applied.　Program-wide　documentation　is　suggested,　both　for　the　purpose　of　internal(71)and　for　later　verification　and(72)efforts:　The　documentation　system　we　propose　includes　a　central　"knowledge　acquisition(73)"which　is(74)to　reflect　knowledge　acquisition　plans,　session　nodes,　and　domain　expert　participation.　Specifically,(75)within　the　database　system　include　knowledge　acquisition　forms,　which　document　plans　for,　and　notes　from,　knowledge　acquisition　session,　domain　expert　file,　and　rule　content　forms.

(60)

You　want　to　use　the　Web　to　let　Eternal　users　or　your　customers　look　at　corporate　information.　But　you　want　to　keep　installation　at　the　user　end(66)and　you　don't　want　just　anyone　to　get(67)your　databases.

That　may　be　where　an　application　server　enters　the　picture.　For　more　user　machine　independent,　these　t　software　packages,　typically　written　in　the(68)programming　language.

for　use　on　Windows　NT-based　systems,　act　as　go-betweens　linking　browser-equipped　　end　users　to　the　databases　that(69)the　information　they　need　to(70)。

(59)