You are on page 1of 21

ASN DEGREE & P.G.

COLLEGE
TENALI

Analysis Report
On

ONLINE DISCUSSION FORUM

Submitted By
B.Bhagya Lakshmi,
VI th sem M.C.A.,
Roll No: 22.

1. Objective:Online discussion forum is just line any another discussion forum found in
most of the websites online with an additional unique elegant look and feel and extended
functionality. The idea of forum has been adopted from lots of forum in many websites.

2. Scope: The ability for posting a message, grouping the messages and replying the
messages.
The ability to become a member in more than one team.
Ability to create more than one team.
Ability to access the existing files.
Ability to place the done projects in the forum.

3. Existing System:The ancient websites are developed by the ASP technology and now in
recent modern era we are going to migrate from ASP to ASP DOTNET
technology. The old websites used to update files only when server is down.

4. Proposed System:ODF is designed in such a way that the whole forum structure is fully
intertwined and tangled within itself. This makes the forum structure very
difficult to empathize. Though it is difficult to comprehend, it can easily be
adaptable to any type of or nature of discussion forum.

5. Software Requirements:Operating System: Windows XP or Higher


I DE

: Visual Studio .NET 2005/2008.

Front End

: ASP.NET

Language

: C#.NET

Database

: Sqlserver 2000/2005.

6. Hardware Requirements:Intel P4 : 1.5GHz or above


512 MB RAM
80 GB HDD Minimum

7. Product Functionality:Login Maintenance:All the activities of the system will be maintained by the Administrator. The
new member can be joined into the system by the administrator only. The administrator
also allows the virtual office work also. By based on the timecards management he may
remove the accessing privileges of the user. He may also restrict the privileges of the user
by based on his actions.

Teams Management :Different teams can be created easily. For every team there is a team leader.

Threads Management:Here, thread means the query generated by a user and the replies that are
given to a user. A general visitor can also read the existed threads in the system. But a
member can reply to those messages. The member can generate new queries.

Project Management:The member who done the project can place it in the system. It can be
accessed by anybody but they can not modify it. The duration of the project and all the
details of that project are placed in the system.

Profile Management:By based on the member wish he can put his profile as private or public.
Whenever he wishes he can modify his profile.

File Access Management:The visitor or member is able to access the files which they want. The person
who had the privileges can only modify it.

8. Use case Diagram:-

9. Data flow Diagrams:Name of the use case:- Member Registration


Description:A new member who wants to join in the discussion forum has to fill the
registration form. By based on his wish he can put his profile as public.

Precondition:Administrator is already logged in.

Normal flow of events:1. New login name, password and member details are entered.
2. The details are saved in the database.

Flow chart:-

Alternate flow of events:1. A message appears for the duplicated login names.

Post condition: A new loginid is created and a message form will appear by congratulating the user. It
will contain a click to the login form.

Name of the use case:- Joining a new member in the team.


Description:Whenever a user wants to join in a team he will send a message to the team leader.

Precondition:The person is registered member.

Normal flow of events:The user will send a message to the team leader in which team he wants to join.

Flow chart:-

Alternate flow of events:Post condition:By seeing the message request the team leader will add him as a required team
member. To the new team member the congratulating message will be send.

Name of the use case:-

Accessing a file.

Description:The member can access a file which he wants. But he can not modify it.

Precondition:-

Normal flow of events:1. The member will choose a file which he wants to read.
2. Then he will down lode the file.

Flowchart:-

Alternate flow of events:1. The selected file will be downloaded.

Post condition:If the member wants he can save the file.

Name of the use case:- Adding a new member to the existed team.
Description:By based on the user request the member will be added in a team.

Normal flow of events:By based on the member id the member will be joined in a team and a message will
be displayed to him.

Flow chart:-

Alternate flow of events:A new member will be created in the chosen team.

Post condition:A message will be displayed to the user such that he joined as a member in another
team.

Name of the use case:- Sending internal messages.


Description:A member of the forum can send the messages to any member of the forum.

Precondition:Normal flow of events:-

Flow chart:-

Alternate flow of events:Post Condition:The message status will be generated.

Name of the use case:- Updating profile.


Description:The member of the team by based on his wish he can change his profile.

Precondition:The member is already logged in the system.

Normal flow of events:1. Update the profile.


2. Save changes

Flow chart:-

Alternate flow of events:Data base will be updated.


Post Condition:Successful updated message will be given.

Name of the use case:- Folder creation


Description:The team leader or the member of the team can create the folders of their own.

Normal flow of events:1. Create a folder.


2. Give the author name and description of the folder.
3. Place the folder created date.

Flow Chart:-

Alternate flow of events:The members of the forum can read the folder files.

Post condition:A new folder will be placed in the forum.

Name of the use case:- Posting a new query.


Description:The user can post a query which is visible to all the members.

Normal flow of events:The user can send a query to the team.

Flow chart:-

Name of the use case:- Creating time card


Description:Here, the administrator wants some projects. So, he will declare the description,
budget allocation and the deadlines for the project. Any member of the forum who is
interested can do the project and can submit it.

Normal flow of events:The user of the team who are interested can do and submit the project.

Flow cart:-

Alternate flow of events:Post condition:The person who are interested in doing the projects will complete and
submit it.

Name of the use case: - Project creation


Description:The member of the discussion forum who had interest to do the project will do it. The
administrator will declare the budget allocation. The number of hours that the member
worked is noticed. The total time period taken to do the project is noticed.

Normal flow of events:1. The project description is given.


2. The time duration taken to do the project is noticed.

Flow cart:-

Alternate flow of events:The member who done the task, his team name, description about the project will be
placed in the discussion forum.

Post condition:The declared budget allocation will be given to the member who done the task.

Name of the use case:- Deactivation of member login privilege.


Description:The member who are registered but not actively participating (i.e., regularly) actively,
his account will be deactivated by the administrator.

Normal flow of events:Flow chart:-

Alternate flow of events:-

Post Condition:If the user account is deactivated he has register once again to login into the System.

10. Sequential Diagrams:1. Sequential diagram for Posting a query:-

2. Sequential diagram for Adding a member in a team:-

3. Sequential diagram for accessing a file:-

4. Sequential Diagram for Administrator activities:-

5. Sequential diagram for Member activities:-

6. Sequential diagram for Folder creation:-

You might also like