終了

outlook expres look-a-like required

All-in-One Specifications (draft) Version 1.0 Author: Jonathan Leyland Date: 04 April 04/04/2003 User manager · User creation · Account management · Profile editing · Password change · Contact (Address list manager) manager. Users can keep the address books online or on their desktop. An automatic synch/updater can be used to synchronies the web based private list. · Private list manager. Share it with other users or make it public. To be decided. Shared lists are when a user sets read-only/write/modify/delete rights to another group of users or another user · An account manager that shows the paid and unpaid services that the user has subscribed to. When a user registers, an email account is supplied to him. He gets a basic package and this can be upgraded on extra payment. When a person joins, he is uniquely identified by his email address or his user id. The system has to cater to that many number of user ids, email server space etc. For corporate users, a single id can be given and the user can then setup his utility to split that into multiple user ids and manage the usernames and profiles. A user can decide whether he should be added to the public lists. The user when creating a contact can collect necessary info for SMS, video, audio messaging, list preferences, group classification etc. When a user registers, he/she can specify his/her interests/preferences for information. These ‘interests’ can be made public. Users can thus find others who are interested. So groups are either public groups/communities or user created. User can invite other users to join these communities. The system will bring together communities, which do similar work. Each activity should have a title??? Communication · SMS · Fax · Chat (Text/Audio/Video). User management on the server · Activation/Deactivation of users General Administration on Server · Messaging to all users or select category of users Advertisement management · Advertisement scheduling · Advertisement configuring - for eg. Targeting to select category of users etc Email on the desktop Basic functions of a standard mailing application Message threading??? Email management on the server · When a user registers, an email account is supplied to him. He gets a basic package and this can be upgraded on extra payment. Document manager Ftp setup Document space Shared document space. Sharing management Email blaster · List subscription manager (a facility to subscribe to a package - say send mail to 5000 email addresses per week plan). Client can drag and drop a list into his desktop. · HTML template builder. Using the template creation utility, the user should be able to create multiple templates and save them. User must be able to merge the list into the template when sending. This html template can be associated with one or more lists. · HTML template management (Edit/Delete/Configure) · Email submission to list (Email blasting) · Statistics/Reports List management on the server · Create or load lists · List management (including cleanup). Delete emails, modify, add emails to list etc. Once email goes, the recipient might unsubscribe to the list. This unsubscribe info should be logged as a transaction and acted upon. If the mail bounces, this email address should be taken off - list cleaning. · email categorization · New categories to be created/deleted or modified Site submission Engine · Subscription manager (a facility to subscribe to a submission package) · Website info management · Submission engine · Results tracking/Statistics/Reports Website Analysis Toolkit · Page optimization · Meta tag generator Site submission manager on the server · Configure parameters for search engine submissions Knowledge management Capture search keywords, urls etc, and deliver-personalized results. Collect similar documents and deliver similar services, add on to the favorites, make communities automatically. Webmaster toolkit · Store house for usernames, passwords, and ftps info, email info, subscription info etc. Service management (server) · Services (or applications) will reside on the server. We should be able to install services and define the subscription mode for these services. The user should be able to browse through the services and subscribe to these. (Drag and drop to his desktop) The entire service is not downloaded, only references are. An example of a service is ‘Site Submission’. · Under a service there can be many packages. Packages can be free or paid. Payment can be for a certain period, or per usage or per click. · When the user downloads this software and registers online, he is given a set of services free. Which services are free need to be decided. · Third parties can submit their applications (services) on to the site. These can be plugged to the payment manager. And configured for pay per usage/pay per click etc. User interface considerations · Space for advertisement · Locale setting · Platforms Personalization · The desktop utility will be a sort of search engine/browser, advertising mechanism/screen saver etc. until the user logs in. On logging in, the application downloads the user’s preferences and configures itself. · When the user moves to another location, he can download the shell from the web. Login and find that the shell personalizes itself for the user. Its skin and services changes according to the user. Web Browsing/Searching · The utility can connect to other http servers also. · Internet searching functions. (Using google API or direct??)The search requests are logged at the server level and then the utility is left to search. These search key words captured can be used to determine the user’s information needs and preferences. · The search engine inside the server will do intelligent search and collect urls, ezines etc for the user. Also will prompt him to add himself to lists, which serve the information. · A favorites manager. The user can transfer his favorites from Internet Explorer and store it in the utility or on the web. (This can later form the base of a web directory if the user provides public access to his favorites folder.). The urls collected during intelligent searching will get added on to the favorites as ‘system supplied’. The user can either delete them or use them. Other utilities · Calculator(s) (Ordinary/Scientific) · World time · Calendar/Appointments/Diary/organizer · Currency converter · Web based utilities (portfolio management/accounting) · Weather · Web based presentation tool · Web based business tool kit · Import Export manager · Hobby manager · Resume and job search · Other services like air tickets/travel/holiday planner etc. Other considerations · Corporate accounts · Concept of adapters to control say EPABXs etc · Privacy settings. · Child protection · Antivirus block · Server considerations Peak capacity - send say 1 million mails a day Store 50000-user information Bandwidth to cater to x number of users online on chat Technological breakthroughs required Intelligent searching All-in-one Copyright 2003.

スキル: .NET, C#プログラミング, マイクロソフトアクセス, PHP, ソフトウェアアーキテクチャ

採用者について:
( 0件のレビュー )

プロジェクトID: #16874437