Use WSS or not - Suggestions needed

Hi

We are developing a web application. The application tracks POs,
Invoices etc. The POs are generated elsewhere, but there are nightly
batch feeds to our system. We have different user levels, with
different permissions.

Now, we want to know if this application can be built in WSS (Is it
really required or not).
f the application is built using WSS, will there be any plus points (in
terms of non-functional requirements like performance, availability
etc) when compared to the application developed without WSS (i.e.,
developed using pure ASP.NET and SQL server)?

Suggestions welcome.


Thanks
Prasanth

HeatherSolomon
Fri Jul 29 09:51:07 CDT 2005

From the requirements you listed out, I don't see the need for WSS. WSS is
a team collaboration tool, seems like you need a custom app to display the
data. You may spend as much or more time customizing WSS to meet your needs
than if you had just put together a custom app.

Unless you plan on using the out of the box features of WSS, or have to hook
it into an existing WSS environment, I see no need for it.
--
Heather Solomon
http://www.heathersolomon.com/blog


"prasanth.krishnan@gmail.com" wrote:

> Hi
>
> We are developing a web application. The application tracks POs,
> Invoices etc. The POs are generated elsewhere, but there are nightly
> batch feeds to our system. We have different user levels, with
> different permissions.
>
> Now, we want to know if this application can be built in WSS (Is it
> really required or not).
> f the application is built using WSS, will there be any plus points (in
> terms of non-functional requirements like performance, availability
> etc) when compared to the application developed without WSS (i.e.,
> developed using pure ASP.NET and SQL server)?
>
> Suggestions welcome.
>
>
> Thanks
> Prasanth
>
>