Đề tài Doctor WebForum

eProject Report Doctor_WebForum Class name: C0909HTeacher name : Bui Duy LinhMember :Vũ Xuân Phương (Team Leader)Vũ Văn SơnLại Thu TrangEmail : xuanphuong1989@gmail.com TABLE OF CONTENT 1. Problem Definition 3 1.1. Problem Abstraction 3 1.2. The Current System 3 1.3. The Proposed System 3 1.4. Boundaries of the System 5 1.5. Hardware and Software Requirements 5 2. Customer Requirements Specification 5 2.1. Users of the System 5 2.2. System functions 6 3. Architecture and Design of Project 10 3.1. Data Flow Diagram 12 3.2. Entity Relationship Diagram(Table Design) 16 3.3. Database Structure 24 4. Flow Chart 30 5. Screen Design 38 6. Checklists 46 7. Task Sheet 46 Problem Definition Problem Abstraction Today, with the development speed quickly of all the branch on the world, has brought about occurring some illnesses that affect the health of mankind. So, medicine is an important branch. There are many different developments from many country on the world. So update information, technology is very important. Internets appear is a favorable condition as a bridge to rub out the places among the countries. Everyone can share the examiner about medicine for the ones on the world by Internet, it’s a Forum about Medicine namely. A Forum about Medicine can satisfy the orders if it can solve the questions bellows: How to view easily the news about Medicine branch on the world? How to register a account to become a member in forum? How to post a query or reply a query (comment) bout medicine to forum? How to search for various Doctors based on the specialization, location, as well it can also include the experience? The Current System Our customer is a doctor who is one of the famous Cardiac specialists in the country. As he is one of the famous specialists in the country, he generally used to visit some places for operating some patients with some critical cardiac conditions. Also he used to get invitations from various colleges in the country for attending and giving the seminars, also he runs a college, which is one of the famous Medical colleges in the country. Actually he wants an online application such as a discussion forum for the doctors in the world, so that if anyone is having any queries (for the junior doctors, etc.) or to discuss some new cases in different fields. He wants this application to be developed as this can bridge the gap between the various doctors available in the world and can know each other through this portal. Also in case of any emergencies or for some special cases one can go through the application and search for the various doctors based on the specialization and the location whichever is suitable so that so many people s lives can be saved. The Proposed System Customer Expectations: The customer wants the application to include the following tasks. There should be a logo common to all the pages of the application, and all the pages should include the symbol of the cross, as a back ground. Through the application one can register online, contact each other through the form where one can post a query and the other can reply. On the home page, the number of users registered (count) and the number of users logged (count) in are to be displayed at the top corner of the page. Also a pop up window is to be displayed where ever necessary like if a user registers or if the user enters a wrong password, etc. As soon as a user registers for the website, the details of the users registered should be counted. There should be an option for the registered users, where his account can be made viewable based on public or private, i.e., if the user don t want to share his contact details, then he can chose the profile to be private, else he can chose the profile to be public. The details should include the contact details, personal, professional, qualification, experience, and as well the achievement details. The Advanced search option is to be included that includes the location, specialization, and as well it can also include the experience. There should be separate login for the admin and as well the users. The users should only be able to can update his / her a/c., access the details, i.e., can only retrieve the details of the other doctors or users, post a query or a request, reply to a query or suggest The Administrator, will have the right of removing or deleting the user An Forum application should be created that will provide the following functions: The Administrator should be able to delete the details of the doctors who are registered with the site. The new discussion topics or queries posted or replied will be displayers with the brief explanation on the homepage, accompanied with a link for accessing the detailed description of the topic or query. While registering, the customer can set the status as private or public. The registered users after log in their account, they can perform the following actions: The user should be able to view the list of the registered users and their details. The user should be able to post a query, reply to a query, discuss some pf the points. The user should be able to view the quries that are posted by the other members of the forum. The user should be able to enter the details of personal, qualification, professional, work, and the achievement related details. The customers after login in his/her account, the can view the details of the queries and the discussion that are posted or replied by them till date. Boundaries of the System Software Library Management Book of we, have size small only use to a school, university … Hardware and Software Requirements Hardware Requirements Recommended Requirements • Pentium IV 1Ghz or over. • Ram over 256MB • Hard disk require over 5 GB free Minimum Requirements • PIII .500Mhz • Ram minimum 128MB • Hard disk require over 1 GB free Software Requirements • Microsoft Windows 2000/XP/Server 2003/Vista… • SQL server 2005 tools to manage database with Microsoft Visual Studio 2005 programming language tool. • Microsoft .Net Framework 2.0 or higher • IIS 5.0 or higher Customer Requirements Specification Users of the System The object influence system includes: Visitor. Doctors Admin. System function. 2.2.1. Administer a system:     Login system : Purpose: Allow uses to declare identification to used program. Object used: Administrator. Functional request: Allow user inputting username and password and validate information. The program will display error if username or password is invalid. Execute condition: Members management : Purpose: Allow manager to manage user information and distribute to every people in system. Object used: Administrator. Functional request: The program must allow user to searched, edited and listed group of users in system. The program allows view user’s information. Execute condition: Manager has to login system. Event management: Purpose: Allow manager to manage user reply and post in system. Object used: Administrator. Functional request: The function must allow user to view, search, edit, delete event of users in system. The function allows to setup publish or unpublished of event. Execute condition: Manager has to login system. Confirm registration of new user : Purpose: Allow manager to confirm registration of new user in system and Change password of user. Object used: Administrator. Functional request: The function must allow manager to register users in system include ID, password. The program allows changing password and ID of user. Execute condition: Manager has to login system. 2.2.2. User system: Login system : Purpose: Allow user to declare identification to used program. Object used: Doctor. Functional request: Allow user to input username and password and validate information. The program will display error if username or password is invalid. Execute condition: User has to login system. Search information : Purpose: Allow user to search information with combo box Advanced search option is to be implemented, so that one can fetch the details with more than one option at a time. Object used: User. Functional request: Allow user to search with more than one option. The program will display result search detail. Execute condition: User has to login system. View information detail : Purpose: Allow user to view information detail. Object used: User. Functional request: Allow user to view detail information. The program will display sorted results according to options that user wants. Execute condition: User has to login system. Message: Purpose: Allow users to send and receive message to other users. Object used: User. Functional request: Allow user to sent message to another user. The program must allow user to view, receive in system. Execute condition: User has to login system. Edit profiles: Purpose: Allow user to edit information detail. Object used: User. Functional request: Allow user to view detail information. Allow user to change user profile. Execute condition: User has to login system. Post : Purpose: Allow user to post in forum. Object used: User. Functional request: Allow user to view detail information. Allow user to post. Execute condition: 2.2.3. Visitor system: Search information : Purpose: Allow user to search information with combo box Advanced search option is to be implemented, so that one can fetch the details with more than one option at a time. Object used: Visitor. Functional request: Allow user to search with more than one option. The program will display result search detail. View information detail of doctor : Purpose: Allow user to view information detail. Object used: Visitor. Functional request: Allow visitor to view detail information. The program will display sorted results according to options that user wants. Post : Purpose: Allow user to post in support forum, not in doctor forum. Allow user to reply in support forum, and in doctor forum. Object used: Visitor. Functional request: Allow visitor to view detail information. Allow visitor to post and reply. Architecture & Design of Project The application will have three- tier data processing model. Tier 1 Web - Tier Tier 2 Middle - Tier Tier 3 Database - Tier User interface with HTML and ASPX page C# (Code - behind) files containing business logic SQL Server 2005  Data Flow Diagram Level 0: Guest Doctor Web Forum Doctor Admin Information changed Information details List of post Post, gets details Post, doctor details List of post Level 1: Admin Doctor Doctor Admin Manager information details Manager Doctor forum Manager Sub forum Manager Support forum Search Manager user Visitor, Doctor, Admin Doctor web forum Details of thread Details of thread Information changed Information Post of doctor Post of doctor User detail User detail List of doctor, list post Post of visitor Post ofvisitor Admin Admin, doctor Admin, doctor Change avatar Change information Change Email, password Set public for information User, UserCP New permission New information New image URL Permission view their information Information New email, password Email, password Admin Admin Add new Edit name Changepermission Delete Sub forum Id New information New forum Name Feed Back Information New permission Permission post and rely Feed back Doctor, visitor Admin Add new Edit name Changepermission Delete Post Id New information New forum Name Feed Back Information New permission Permission post and reply Move post Post Post Feed Back Name, title, content, Entity Relationship Diagram(Table Design) Entity “Categories” Categories CategoryID CategoryName DateCreation Priority Entity “MemberProfiles” MemberProfiles MemberID RoleID Blast Avatar Country Address BirthDay Hospital Gender Yahoo Phone TotalThanked Hospital TotalPosts Blog LastLogin TotalThanks Signature AboutMe Professional Experience Entity “Member” Member MemberID UserName Password Email FullName DateCreation AllowLogin IsPublic IsOnline IsPublic Entity “Post” Posts PostID TopicID MemberID [Content] DateCreation DateEdited Signature QuoteID Entity “RatingPost” RatingPost RatingPostID FromMember PostID RatePoint RateDate Entity “RatingTopic” RatingTopic RateTopicID FromMember TopicID RatePointion RateDate Entity “Roles” Roles RoleID RoleName Description TotalPosts RankImage Entity “SubForum” SubForums SubForumID CategoryID SubForumName Description DateCreation Priority TotalTopics TotalMessages Entity “ThankPost” ThankPost ThankPostID ThankDate PostID FromMember Entity “RatingTopic” ThankTopic ThankTopicID ThankDate TopicID FromMember Entity “Topic” Topics TopicID DateEdited SubForumID MemberID Title [Content] TotalViews TotalMessages DateCreate MoveTo IsLocked E-R Diagrams Database Structure Table : Members Field Name Data Type Null Key Description MemberID Int No PK Stores the ID of Member UserName Nvarchar(30) Yes Stores the of User Member Password Nvarchar(50) Yes Stores the password of Member Email Nvarchar(100) Yes Stores the email of Member FullName Nvarchar(50) Yes Stores the fullname of Member DateCreation DateTime Yes Stores the created date of Member’s account AllowLogin Bit Yes Check if Member’s account is lock or not IsPublic Bit Yes Check if Member is public or not IsOnline Bit Yes Check if Member is login or not Table: ThankTopic Field Name Data Type Null Key Description ThankTopicID Int No PK Stores the ID of ThankTopic FromMember Int No FK Stores the ID of Member TopicID Int No FK Stores the ID of Topic ThankDate Datetime Yes Stores the date of ThankTopic Table : MemberProfiles Field Name Data Type Null Key Description MemberID Int No PK,FK Stores the ID of Member RoleID Int No FK Stores the RoleID of Roles Blast Nvarchar(100) Yes Stores the blast of Member Avatar Nvarchar(150) Yes Stores the avatar of Member Country Nvarchar(50) Yes Stores the country of Member Address Nvarchar(255) Yes Stores the address of Member BirthDay Datetime Yes Stores the birthday of Member Gender Bit Yes Stores the gender of Member Yahoo Nvarchar(100) Yes Stores the Yahoo account of Member Phone Nvarchar(15) Yes Stores the phone of Member Hospital Nvarchar(100) Yes Stores the hospital where Member works Blog Nvarchar(100) Yes Stores the blog account of Member TotalPosts Int Yes Stores the quantity post of Member TotalThanks Int Yes Stores the quantity thanks of Member TotalThanked Int Yes Stores the quantity thanked of Member CurrentExperience Float Yes Stores the Current Experience of Member Professional Nvarchar(255) Yes Stores the Professional LastLogin DateTime Yes Stores the date lastlogin of Member Signature Nvarchar(1000) Yes Stores the signature of Member AboutMe Ntext Yes Stores the about of Member Table: Categories Field Name Data Type Null Key Description CategoriesID Int No PK Stores the id of Category CategoryName Nvarchar(50) Yes Stores the name of Category Priority Int Yes Stores the date priority of Category DateCreation Datetime Yes Stores the date create of Category Table: ChatMessages Field Name Data Type Null Key Description ChatID Int No PK Stores the ID of ChatMessages MemberID Int No FK Stores the ID of Member ChatContent Ntext Yes Stores chatcontent of ChatMessages ChatDate Datetime Yes Stores chat date of ChatMessages Table: Messages Field Name Data Type Null Key Description MessageID Int No PK Stores the ID of Message FromMember Int No FK Stores the ID of ToMember Int No FK Stores the ID of Title Nvarchar(100) Yes Stores the title of Message MessageContent Ntext Yes Stores the message content of Message Datesend Datetime Yes Stores the date of sending Message IsView Bit Yes Stores the enable or disable view IsRead Bit Yes Stores the enable or disable read. Table: Moderator Field Name Data Type Null Key Description SubForumID Int No PK,FK Stores the ID of Moderator MemberID Int No FK Stores the ID of Member Table: Posts Field Name Data Type Null Key Description PostID Int No PK Stores the ID of Post TopicID Int No FK Stores the ID of Topic MemberID Int No FK Stores the ID of Member Content Ntext Yes Stores the content of Post DateCreation Datetime Yes Stores the date of Post DateEdited Datetime Yes Stores the date when Member edit Post Signature Bit Yes Stores the signature of Member QuoteID Int Yes Stores the ID of PostID Table: RatingPost Field Name Data Type Null Key Description RatingPostID Int No PK Stores the ID of RatingPost FromMember Int No FK Stores the ID of Member Rating to Post PostID Int No FK Stores the ID of Post RatePoint Int Yes Stores the rate point of Post RateDate Datetime Yes Stores the rate date Table: RatingTopic Field Name Data Type Null Key Description RateTopicID Int No PK Stores the ID of RatingTopic FromMember Int No FK Stores the ID of Member Rating to Topic TopicID Int No FK Stores the ID of Topic RatePoint Int Yes Stores the point of Rating RateDate Datetime Yes Stores the rate date Table: Roles Field Name Data Type Null Key Description RoleID Int No PK Stores the ID of Roles RoleName Nvarchar(20) No Stores the name of Roles Description Nvarchar(100) Yes Stores the TotalPosts Int Yes Stores Quantity of Post RankImage Nvarchar(100) Yes Stores rank image Table: SubForums Field Name Data Type Null Key Description SubForumID Int No PK Stores the ID of SubForum CategoryID Int No FK Stores the ID of Category SubForumName Nvarchar(100) No Stores the name of SubForum Description Nvarchar(500) Yes Stores the description of Subforum DateCreation Datetime Yes Stores the DateCreation of Subforum Priority Int Yes Stores the Priority of Subforum TotalTopics Int Yes Stores the TotalTopics of Subforum TotalMessages Int Yes Stores the TotalMessages of Subforum Table: Topics Field Name Data Type Null Key Description TopicID Int No PK Stores the ID of Topic SubForumID Int No FK Stores the ID of SubForum MemberID Int No FK Stores the ID of Member Title Nvarchar(100) Yes Stores the title of Topic Content Ntext Yes Stores the content of Topic IsLocked Bit Yes Stores the status is locked TotalViews Int Yes Stores the quantity of View TotalMessages Int Yes Stores the quantity of Message DateLastPost Datetime Yes Stores the DateLastPost of Message MoveTo Int Yes Stores the MoveTo of Message DateEdited Datetime Yes Stores the Date if Member Edit Coment Table: ThankPost Field Name Data Type Null Key Description ThankPostID Int No PK Stores the ID of ThankPost FromMember Int No FK Stores the ID of Member PostID Int No FK Stores the ID of Post ThankDate Datetime Yes Stores the date of ThankPost Flow Chart Flow Chart Login Admin Begin End User name or Password invalid Check Admin Account Input Usernames, Password Access system False True Flow Chart Login User Begin End Yes or no Check userAccount Input Usernames, Password Access system False True Flow Chart Register Begin End Validation Register from display Inputinformation User management True Save database Decentralization for new user Informationvalidate False False Flow Chart Search Begin End Valid? Check keyword Inputkeyword True Checkd