Online College Magazine: Submitted As Part of The Non-Syllabus Activity

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 20

SECOND YEAR NON-SYLLABUS PROJECT SRS

ONLINE COLLEGE MAGAZINE

Submitted As Part of the Non-Syllabus Activity

By

SURABHI GUPTA (CE/10/109)


PURVI GARG (CE/10/)
SHIVAM KUMAR(CE/10/)

DEPARTMENT OF COMPUTER ENGINEERING


POORNIMA INSTITUTE OF ENGINEERING & TECHNOLOGY, JAIPUR
(Academic Year 2011-12)
Table of Contents:

1.0 Introduction
1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms, and Abbreviations
1.4 References
1.5 Overview

2.0 Overall Description


2.1 Product Perspective
2.2 Interfaces
2.2.1 System Interfaces
2.2.2 User Interfaces
2.2.3 Software Interfaces
2.2.4 Hardware Interface
2.2.5 Communication Interface
2.3 Product Function
2.4 User Characteristics
2.5 Constraints
2.6 Architecture Design
2.6.1 Process Model
2.7 Process Flow Diagram
2.7.1 DFDs
2.8 Database Design
2.8.1 ER Diagram
2.9 Use Case Diagrams
2.10 Assumptions and Dependencies
1.0 Introduction:

Creating and managing an Online College Magazine where college students and faculties
can post and read various articles, thus promoting literary insight. Articles can be
searched by anybody in the world.

When a project is started an initial investigation is carried out. During this phase of
study users need has recognized and other requirements are determined. Once the
problem has been defined a study is carried out to select the best system i.e. a feasible
system that meets performance requirements. So Feasibility is the determination of
whether or not a project is worth doing and the process followed in making this
determination is called a Feasibility Study. In order to conduct the feasibility study we
have seven distinct, but inter-related types of feasibility, these are Technical feasibility,
Operational feasibility, Economical feasibility, Social feasibility, Management feasibility,
Legal feasibility and Time feasibility.
Out of these seven three are key feasibilities to consider, those are:

• Technical Feasibility
• Economical Feasibility
• Operational feasibility

TECHNICAL FEASIBILITY:
This is concerned with specifying equipment (hardware) and software that will
successfully satisfy the user requirement. It considers the following facts:

• The facility to produce outputs in a given time.


• Response time under certain conditions.
• Ability to process a certain volume of transaction at a particular speed.
• Facility to communicate data to distant location.
While examining technical feasibility, huge importance is given to the configuration of
the proposed system. The configuration should give the complete picture about the
system’s requirement such that what kind of hardware is required and how these units
are interconnected so that they could operate and communicate smoothly.

Configurations will be pursued that satisfies the key technical requirements but
represent different levels of ambition and cost.

ECONOMICAL FEASIBILITY:
Since cost plays quite an important role in deciding the new system, it must be
identified and estimated properly. So economic analysis is the most frequently used
technique for evaluating the effectiveness (economical feasibility) of a proposed system.
To determine the economical feasibility of the system a cost/benefit analysis is to make.
This procedure is to determine the benefits and savings that are expected from a
proposed system and compare them with costs. Four facts that play an important role in
deciding economical feasibility of the proposed system are as follows:

• Cost-saving benefits
• Cost-avoidance benefits
• Improved-performance benefits
• Improved - information benefits.
Hence the proposed system is economically feasible.

OPERATIONAL FEASIBILITY:
It is mainly related to human organizational aspects. The points to be considered are:
• What changes will be brought with the system?
• What organizational structures are disturbed?
• What new skills will be required?
• Do the existing Employees members have these skills if not, can they be trained?

EXISTING SYSTEM:
The existing systems of Online College Magazine of various colleges provides lots of
features but all these Websites are public. Anyone can have an account on these. Such
Websites are not secured for updation of critical information about college. Due to this,
a private Website for College has been established. Only Administrator can post Article
earlier but now student can also share ideas.

PROPOSED SYSTEM:

Online college Magazine website has various benefits with which we all are quite
familiar. The proposed system has been established for college students, faculty and
guests. In this Website, only the authorized users can login. Many features like all other
Websites has been tried to be implemented. The flexibility of this system will definitely
help Students to communicate with each other very easily.

1.1 Purpose:

Creating and managing an Online College Magazine where college students and faculties
can post and read various articles, thus promoting literary insight. Articles can be
searched by anybody in the world. Factors behind the motivation of this system are:

1. Not all students make it to the printed magazine.


2. Creativity of students needs to be nurtured.

Creating a user-friendly interactive place where students/faculties can share their


ideas.

1.2 Scope:

The Scope of the ONLINE COLLEGE MAGAZINE includes:

 User must have a valid User Id and password to login to the system.
 If a wrong password is given thrice in succession, that account will be locked
and the
customer will not be able to use it. When an invalid password is entered a warning
is given
to the user that his account is going to get locked.
 Search Engine for all the articles posted till date. Accessible by anybody.
 Essential steps to be taken to prevent authenticity infringement.
 Articles to be distributed in categories. Can overlap 2 or more categories.
Articles to be associated with suitable tags by the registered users at the time
of posting, so that they are searchable.
 The home page to consist of attractive essential features like: most read
articles, editor’s pick, recently posted articles, highest rated articles, article of
the month, college news, etc.
 Archives to be maintained.
 Interactive feedback to be supported to enhance the user experience.
 Guests can read articles, rate them and comment on them. They can also access
other optional features (amenities like Word of the day, etc.) but can’t post
articles unless they sign in as registered users.
 Automatic commenting on articles by spammers/automatic bots to be defied.
 College Students/Faculties can only register as members (through unique IDs).
 Alumni registration to be supported.
 Registered members, Moderators and Administrators are allowed to post
articles.
 Articles can be downloaded in various formats.
 Registered users, Moderators, and Admins will have their own profile, where
they can edit info for the world to see. Useful “updated” info related to their
activities to be available at their profiles.

1.3 Definitions, Acronyms, and Abbreviations:

• HTML (Hyper Text Markup Language): It is used to create static web pages.

• JSP (Java Server Pages): It is used to create dynamic web content.

• J2EE (Java 2 Enterprise Edition): It is a programming platform,


belonging to the Java platform, which is used for developing and running
distributed java applications.

• WASCE (WebSphere Application Server Community Edition): It is an


application server that runs and supports the J2EE and the web service
applications.

• WSAD (WebSphere Studio Application Developer ): It is a designer


toolkit which is designed to develop more complex projects by providing a
complete dynamic web service.

• DB2 (IBM Database 2): It is a database management system that


provides a flexible and efficient database platform to raise a strong "on
demand" business applications.
• HTTP (Hyper Text Transfer Protocol): It is a transaction oriented
client/ server protocol between a web browser and a web server.

• XML (Extensible Markup Language): It is a markup language that


was designed to transport and store data.

• Ajax (Asynchronous Java Script and XML): It is a technique used in


java script to create dynamic web pages.

• Web 2.0: It is commonly associated with web applications which


facilitate interactive information sharing, interoperability, user-centered
design and collaboration on the World Wide Web.

1.4 References:
 SRS (IEEE SRS Format and Format provided by TGMC).
 Project specification requirement (provided by TGMC).
 Problem Definition (provided by TGMC)
1.5 Overview:The SRS will include two sections, namely:

 Overall Description: This section will describe major components of the


system, interconnections, and external interfaces.
 Specific Requirements: This section will describe the functions of actors,
their roles in the system and the constraints faced by the system.

2.0 Overall Description:

2.1 Product Perspective:

The client will have client interface in which he can interact with the
banking system. It is a web based interface which will be the web page of
the banking application. Starting a page is displayed asking the type of
customer he is whether ordinary or a corporate customer. Then the page is
redirected to login page where the user can enter the login details. If the
login particulars are valid then the user is taken to a home page where he
has the entire transaction list that he can perform with the bank. All the
above activities come under the client interface.
The administrator will have an administrative interface which is a GUI so
that he can view the entire system. He will also have a login page where he
can enter the login particulars so that he can perform all his actions. This
administrative interface provides different environment such that he can
maintain database & provide backups for the information in the database.
He can register the users by providing them withusername, password & by
creating account in the database. He can view the cheque book request &
perform action to issue the cheque books to the clients.
2.2 Interface
2.2.1 Software Interface:

 User on Internet : Web Browser, Operating System (any).


 Application Server : WAS
 Data Base Server : DB2
 Network : Internet
 Development Tools : WSAD (J2EE,Java,Servlets,HTML), DB2, OS(Windows),
Application Server.

2.2.2 Hardware Interface:


CLIENT SIDE

Processor Ram Disc Space

Internet Explorer Pentium II at 64 MB 1 GB


7.0 500 MHz

SERVER SIDE
Web sphere Pentium III at 512 MB 2 GB
application server 1 GHz
V5.0
DB2 V8.1 Pentium III at 512 MB 1GB
1 GHz (Excluding data
size)

2.3 Product Functions:

• Search Engine for all the articles posted till date. Accessible by anybody.

• Essential steps to be taken to prevent authenticity infringement.

• Articles to be distributed in categories. Can overlap 2 or more categories.


Articles to be associated with suitable tags by the registered users at the time of
posting, so that they are searchable.

• The home page to consist of attractive essential features like: most read
articles, editor’s pick, recently posted articles, highest rated articles, article of the
month, college news, etc.

• Archives to be maintained.

• Interactive feedback to be supported to enhance the user experience.

• Guests can read articles, and comment on them. They can also access
other optional features (amenities like Word of the day, etc.) but can’t post
articles unless they sign in as registered users.
• College Students/Faculties can only register as members (through unique IDs).

• Alumni registration to be supported.

• Registered members and Administrators are allowed to post articles.

• Articles can be downloaded.

• Registered users, and Admins will have their own profile, where they can edit info
for the world to see. Useful “updated” info related to their activities to be available at
their profiles.

• Moderators will have associated categories, according to which to-be-validated-


articles will be posted to them on their profiles. On rejection, he will have to provide a
reason for the same, which will be forwarded to the concerned user.

• Mails to be sent on rejection/acceptance of articles.

2.4 User Characteristics:

User should be of particular college. He/she should be student or faculty


Of that college. They can post articles,download articles,etc.

2.5 Constraints:

o Login and password is used for identification of customer’s account and


there is no facility for non users to login.
o This system works only on a single server.
o GUI is only in English
o Limited to HTTP/HTTPS protocols
2.7 DATA FLOW DIAGRAMS

LEVEL 0 DFD

Home Items
Page List

LEVEL 1 DFD

New

Hom User
e Items
Page List

Existe
d

User
LEVEL 2 DFD

Registratio
New n Form

User

Databa
User se

Home
ID
Page

Login

Page

Items

List
LEVEL 3 DFD

Flo
wer
s

Gift
s

Home Items
Add
Page List
E-
To
de
Cart
vice
s

Jew
eller
y
LEVEL 4 DFD
Modif
y

View

Cart

Hom
Items Add
e
List Cart
Page

Bill

Credi
t
Card

LEVEL 5 DFD

Credi
Data
t
card base
2.8 ER Diagram:

us
er
password
Student id address
Admin id password
Phone no

manages Student
administrator

manages
Works in

Org_name User

College

Feedback
Accounts_types

Upload Article Download Comment Rate Article


manage

Generate Grant Perform Checks


the request the
accounts Action available
Grant Perform
request action

Internal_admin

Admin id

password

displays

2.9 Use Case Diagram :

.
Description and the priority of this system:

• When we consider the online college magazine in this we provide the


details of how to access the magazine without going to the bank through
internet.
• When we consider the priority of this project it is mainly of medium cost, efficient
to user access data, provides the required data, safe and secure one,we can know
the details of our account.
LO G I
N

a c c o u n t li s t
in it ia lis e s

S tu d e n t
D o w n lo a d a r t ic le
s t a r t s e s s io n s

U p lo a d a r t ic e
D ata B ack u p
PERFO RM S

u p d a t e p r o fil e a d m in is tr a t o r
C ra sh re co v e ry

Feedback

E n d s e s s io n s
G u est
Com m ent

sh u td o w n s
h e lp

lo g o u t
A C T IV IT Y D IA G R A M FO R O V E R A LL S Y S T E M

START

Username
and

no
valid user

yes

UPLOAD DOWNLOAD update profile COMMENT FEEDBACK

ARTICLE ARTICLE

SUCCESSFU SUCCESSF
: .
LL ULL

Log out

STOP

2.10 Assumptions and Dependencies:

 The details of customers such as username, password, account type and


their corresponding authority details should be manually entered by the
administrator before using this system.
 Every user should be comfortable of working with computer and net
browsing.
 He should be aware of the banking system.

 He must have basic knowledge of English too.

You might also like