university student bulletin

UNIVERSITY STUDENT BULLETIN

Presented by: Karthik Gangupalli Niraj SharmaPaul StanleyShabnam BoparaiShreeti PandeySumeet Pawar

Content1. Scope

2. Objectives

5. Benefits of a web-based bulletin6. Team roles and responsibilities

9. Feasibility analysis

4. Limitations of traditional bulletin board

8. Risk7. Project Plan

3. Problem definition

1.ScopeProvides new, current students and alumni information on used and new items for purchase on the web: Items - include books, furniture items,

cars and apartment leases Open only to current students and

alumni to post and search listings

2.Objectives Replace physical bulletin boards and do

away with their cost of maintenance

3. Problem definition UHCL does not have an online Bulletin Board where

students can post information on items for sale Currently flyers approved by Student Life are

posted on traditional bulletin boards in the Bayou Building

Due to limited space on the physical board, over time flyers get covered with other postings, students could miss some postings

Time consuming to look for relevant postings Expired and unauthorized flyers have to be

physically removed

4. Limitations of Traditional Bulletin boards

• Hard to read• Time consuming• Unorganized• Overcrowded• Missing information• Easy to remove• Difficult to regulate• Difficult to maintain

5.Benefits of a Web-based Bulletin

Quick and convenient way to exchange information

Assist students moving for jobs/internships by providing easy access to information

Easy to regulate and maintain Searchable Scalable User friendly Environment friendly

6.Team Roles & Responsibilities

Project Manager: Sumeet Pawar Systems Architect: Paul Stanley Systems Analyst: Shabnam Boparai Database Analyst: Shreeti Pandey Developers: Karthik Gangupalli, Niraj

Sharma

7.Project Plan The team will conduct the following

activities: Conduct needs assessment Document product scope Design the system Construct the data flow diagrams Develop a timeline for developing the

system Develop the system

7.Project Plan (Contd…) Test the system Evaluate the system Make changes if required Conduct usability testing of the web

interface Redesign front-end if needed Complete system documentation Undertake training activities

8.Risk Low adoption rates

Few students logging on to post listings would affect the popularity of the system as a tool to search for items

Need for university wide promotions and advertisements

9.Feasibility Analysis Technical Feasibility Organization Feasibility

9.1 Technical Feasibility Technically the system is feasible if the

number of items being listed is restricted to – used cars, furniture, apartment leases and books

A miscellaneous section could be provided to post general items

9.2 Organization Feasibility Replace/compliment the traditional

bulletin board Students would benefit a great deal from

such a web-based system Stronger, Faster and Harder to break

such a Web-Based system

Questions and Comments?

THE END