Chapter 1

INTRODUCTION

Online college Magazine is a forum where college students and faculties can post and read various
articles, thus promoting literary insight. Articles can be searched by anybody in the world.

1.1 Project definition: Online College Magazine

The Program can also include feature of categorizing articles, one can give feedback, Rate the article, one can
Search article by category or topic as well. Topics get sorted by constraint of most viewed and tags are attached
to article by number of reads.
The project is an effort to build a professionally look /featured online forum, with an user friendly Interface
and lot of features to grab visitors and provide them lot at a place.
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.
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.

1
 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.
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?

1.2 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.

1.3 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.4 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.

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

1.5 Scope:
 The Scope ofthe 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.

3
Chapter 2
REQUIREMENT ANALYSIS AND SPECIFICATION ANALYSIS

Requirements Analysis is the process of defining the expectations of the users for an application that is
to be built or modified. High-quality requirements are documented, actionable, measurable, testable, traceable,
helps to identify business opportunities, and are defined to a facilitate system design.

2.1SpecificRequirements
2.1.1Admin use-case report

Fig 2.1.1Admin use-case report

Description:

The admin can perform the functions which are displayed above. The admin takes care of the server
up grade and maintenance, website security to prevent spamming and hacks. The admin so takes care of the
design and analysis of the website with the moderator.
4
2.1.2 Alumni use case report

Fig 2.1.2 Alumni use case report

Description:

The admin can perform the functions which are displayed above. The admin takes care of the server
up grade and maintenance, website security to prevent spamming and hacks. The admin so takes care of the
design and analysis of the website with the moderator. The role of selecting the moderator sand up dating them
is done by the administrator The alumni will enjoy limited functions on the website. The alumni can report
articles, view profile of professors, rate articles, and edit his own profile.

2.1.3 Guest use case report

Fig 2.1.3 Guest use case report

5
Description:

The guest does not enjoy all benefits like a registered user. The guest functions Will be limited to
viewing the campus news. The guest cannot rate or comment on articles posted on the online magazine website.

2.1.4 Registered users use case report

Fig. 2.1.4 Registered users use case report

Description:
A registered user enjoys maximum privileges on the online website. The registered user category belongs
to current students and faculty. The registered user can have his own profile, rate and comment on articles
which are posted. Submitting article sand updating the profiles are also a part of the functions which the registered
user can perform.

6
2.1.5 Moderator use case report

Fig 2.1.5 Moderator use case report

Description:

The moderator forms the centre of the online magazine website. He has various functions to perform.
The moderator posts the word of the day on the website, updates the campus news and events, posts thought
of the day and update the library section. The moderator will also, confirm membership, and will have the
privilege of disabling a profile and renewing the password if required. The moderator can block certain
offensive articles of required. The final verdict of selecting the article or rejecting it lies with the moderator.
Hence the moderator forms the most important part of the use-case model.

7
2.2 Class Diagram

Fig.2.2.1 Class Diagram

8
2.3 Sequence Diagrams
2.3.1 Sign-up Sequence

Fig 2.3.1Sign-upSequence

Description:

A sequence diagram shows object interactions arranged in time sequence. It depicts the objects and
classes involved in the scenario and the sequence of messages exchanged between the objects needed to carry
out the functionality of the scenario. Sequence diagrams are sometimes called event diagrams or event
scenarios

9
2.3.2 Report Article Sequence

Fig 2.3.2 Report Article Sequence

Description:

A sequence diagram simply depicts interaction between objects in a sequential order i.e. the order in
which these interactions take place. We can also use the terms event diagrams or event scenarios to refer to a
sequence diagram. Sequence diagrams describe how and in what order the objects in a system function. These
diagrams are widely used by businessmen and software developers to document and understand requirements
for new and existing systems.

10
2.3.3 Article posting Sequence

Fig 2.3.3 Article posting Sequence

2.4 Use Case Reports:

2.4.1 Administrator
 He is the super user responsible for managing clients of the system, taking system backup, generating
reports, maintaining organization details.
 Manage Clients: The Administrator assigns new users when a new client joins the
 Online magazine. Also he can delete an account when any of the clients leave the college organization.
 Maintain Organization Details: The Administrator maintains entire details of the
 Organization that includes details of the clients, entrepreneur details etc.
 Take System Backup: The Administrator Backup the database in order to prevent
 Loss of data on system crashes. He can backup entire database or a particular section.
 Generate Reports: Responsible for checking the logs of different system users for a nd maintaining
the integrity of the system.
 Manage Clients
 Name of Use Case: Manage clients.
 The Administrator assigns new users when a new client joins the online
 Bank. Also he can delete an account when any of the clients leave the bank organization.

11
  Preconditions:
 Administrator is already logged in.

Create account

Manage client Delete account

 Name Of Use-Case: Maintain organizational details

 Description: The Administrator should maintain all the organizational details.
 Preconditions:
 Administrator is already logged in.

Entrepreneur details

Details
Client details

 Name of Use-Case: Take System backup.

 Description: The Administrator Backup the database in order to prevent loss of data
 On system crashes. He can backup entire database or a particular section.
 Preconditions:
 Administrator is already logged in.
 Name Of Use-Case: Generate Reports.
 Description: The Administrator is responsible for checking the logs of different clients
 For auditing and maintaining the integrity of the system.
 Preconditions:
12
 Administrator is already
 Logged in.

2.4.2Customer:
Ordinary customers have a user name & password with which they can login into their account.
 Name of Use-Case: Login.
 Description: Customer must provide a valid User Id and password to login to the system.
 Preconditions:
 Customer must have a valid User Id and password to login to the system.

2.5SupplementaryRequirements:
2.5.1PerformanceRequirements
System can with stand even though many no. of customers request the desired service. Access is given to only
valid user so college who requires the services such as upload article, download article, newsletters, thoughts of
day etc.

2.5.2 Safety Requirements

By incorporating a robust and proven DB2UDB in to the system, reliable performance and integrity of data is
ensured. There must be a power backup for server system. Since the product of 24x7availability there should
be power back up for server which provides the information. Every day the data should be backup Even when
the operation of an user is not successful i.e ,while performing the operation power failure occurs then data
show.

2.5.3 Overview:
 The SRS will include sections, namely:
 Overall Description: This section will describe major components of the system, inter connections, 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.6 E-R DIAGRAM

Description:
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database. By
defining the entities, their attributes, and showing the relationships between them, an ER diagram illustrates
the logical structure of databases. ER diagrams are used to sketch out the design of a database. Database

13
troubleshooting: ER diagrams are used to analyze existing databases to find and resolve problems in logic or
deployment. Drawing the diagram should reveal where it's going wrong. Business information systems:
The diagrams are used to design or analyze relational databases used in business processes.
When we talk about entities in ERD, very often we are referring to business objects such as people/roles (e.g.
Student), tangible business objects (e.g. Product), intangible business objects (e.g. Log), etc. "Relationship" is
about how these entities relate to each other within the system.
Depending on the scale of change, it can be risky to alter a database structure directly in a DBMS. To avoid
ruining the data in a production database, it is important to plan out the changes carefully. ERD is a tool that
helps. By drawing ER diagrams to visualize database design ideas, you have a chance to identify the mistakes
and design flaws, and to make corrections before executing the changes in the database.
To debug database issues can be challenging, especially when the database contains many tables, which require
writing complex SQL in getting the information you need. By visualizing a database schema with an ERD,
you have a full picture of the entire database schema. You can easily locate entities, view their attributes and
identify the relationships they have with others. All these allow you to analyze an existing database and to
reveal database problems easier.
Visual Paradigm, an ERD tool, supports a database generation tool that can automate the database creation
and patching process by means of ER diagrams. So, with this ER Diagram tool, your ER design is no longer
just a static diagram but a mirror that reflects truly the physical database structure.
Determine the requirements of an information system by drawing a conceptual ERD that depicts the high-level
business objects of the system. Such an initial model can also be evolved into a physical database model that
aids the creation of a relational database, or aids in the creation of process maps and data flow modes.
Depending on the scale of change, it can be risky to alter a database structure directly in a DBMS. To avoid
ruining the data in a production database, it is important to plan out the changes carefully. ERD is a tool that
helps. By drawing ER diagrams to visualize database design ideas, you have a chance to identify the mistakes
and design flaws, and to make corrections before executing the changes in the database.
To debug database issues can be challenging, especially when the database contains many tables, which require
writing complex SQL in getting the information you need. By visualizing a database schema with an ERD,
you have a full picture of the entire database schema. You can easily locate entities, view their attributes and
identify the relationships they have with others. All these allow you to analyze an existing database and to
reveal database problems easier.
By incorporating a robust and proven DB2UDB in to the system, reliable performance and integrity of data is
ensured. There must be a power backup for server system. Since the product of 24x7availability there should
be power back up for server which provides the information. Every day the data should be backup Even when
the operation of an user is not successful i.e while performing the operation power failure occurs then data
show.

14
Fig 2.6. E-R DIAGRAM

15
2.7 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.
A UML use case diagram is the primary form of system/software requirements for a new software program
underdeveloped. Use cases specify the expected behavior (what), and not the exact method of making it happen
(how). Use cases once specified can be denoted both textual and visual representation (i.e. use case diagram).
A key concept of use case modeling is that it helps us design a system from the end user's perspective. It is an
effective technique for communicating system behavior in the user's terms by specifying all externally visible
system behavior.
A use case diagram is usually simple. It does not show the detail of the use cases:
 It only summarizes some of the relationships between use cases, actors, and systems.
 It does not show the order in which steps are performed to achieve the goals of each use case.
As said, a use case diagram should be simple and contains only a few shapes. If yours contain more than 20
use cases, you are probably misusing use case diagram. The figure below shows the UML diagram hierarchy
and the positioning of the UML Use Case Diagram. As you can see, use case diagrams belong to the family
of behavioral diagrams.
Use cases share different kinds of relationships. Defining the relationship between two use cases is the decision
of the software analysts of the use case diagram. A relationship between two use cases is basically modeling
the dependency between the two use cases. The reuse of an existing use case by using different types of
relationships reduces the overall effort required in developing a system.
The purpose of use case diagram is to capture the dynamic aspect of a system. However, this definition is too
generic to describe the purpose, as other four diagrams (activity, sequence, collaboration, and Statechart) also
have the same purpose. We will look into some specific purpose, which will distinguish it from other four
diagrams. Use case diagrams are used to gather the requirements of a system including internal and external
influences. These requirements are mostly design requirements. Hence, when a system is analyzed to gather
its functionalities, use cases are prepared and actors are identified.
As said, a use case diagram should be simple and contains only a few shapes. If yours contain more than 20
use cases, you are probably misusing use case diagram. The figure below shows the UML diagram hierarchy
and the positioning of the UML Use Case Diagram. As you can see, use case diagrams belong to the family
of behavioral diagrams. However, this definition is too generic to describe the purpose, as other four diagrams
(activity, sequence, collaboration, and State chart) also have the same purpose. We will look into some specific
purpose, which will distinguish it from other four diagrams. Use case diagrams are used to gather the
requirements of a system including internal and external influences.

16
 Chapter 3
IMPLEMENTATION

A programming language implementation is a system for executing computer programs. There are two
general approaches to programming language implementation: Interpretation: An interpreter takes as input a
program in some language, and performs the actions written in that language on some machine.

3.1 Definitions, Acronym sand Abbreviations:

•HTML(Hyper Text Markup Language): It is used to create static web pages.
•DBMS(Database Management System):It is a data base management system that provides
flexible and efficient database platform to raise a strong "on demand" business applications.

3.2ProductPerspective:
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.
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 with username,
password & by creating account in the database. He can view the check book request & perform action to
issue the check books to the clients.

3.3 Interface
3.3.1 Software Interface:
 User on Internet: Web Browser, Operating System (any).
 Data Base Server : DB2
 Network : Internet
 Development Tools : WSAD (J2EE,Java,Servlets,HTML), DB2, OS(Windows),

3.3.2 Hardware interface:

17
 CLIENT SIDE

Processor Ram Disc Space

Internet Explorer Intel core I3 4GB 1 TB

7.0

SERVER SIDE
Web sphere Intel core I3 4 GB 1 TB
application server
V5.0
DB2 V8.1 Intel core I3 4 GB 1 TB
(Excluding data
size)

3.4 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.

18
 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.

3.5 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.

3.6 Constraints:
 Login and password is used for identification of customer’s account and there is no facility for nonusers to
login.
 This system works only on a single server.
 GUI is only in English
 Limited to HTTP/HTTPS protocols

3.6.1 Activity Diagrams

Activity diagram is another important diagram in UML to describe the dynamic aspects of the system.
Activity diagram is basically a flowchart to represent the flow from one activity to another activity. The
activity can be described as an operation of the system.The control flow is drawn from one operation to
another. This flow can be sequential, branched, or concurrent. Activity diagrams deal with all type of flow
control by using different elements such as fork, join. The basic purposes of activity diagrams is similar to
other four diagrams. It captures the dynamic behaviour of the system. Other four diagrams are used to show
the message flow from one object to another but activity diagram is used to show message flow from one
activity to another .Activity is a particular operation of the system. Activity diagrams are not only used for
visualizing the dynamic nature of a system, but they are also used to construct the executable system by using
forward and reverse engineering techniques. The only missing thing in the activity diagram is the message
part. It does not show any message flow from one activity to another. Activity diagram is sometimes
considered as the flowchart. Although the diagrams look like a flowchart, they are not. It shows different
flows such as parallel, branched, concurrent, and single.

19
Fig 3.6.1Activity diagram for overall system

20
3.6.2 User login Activity

Fig 3.6.1 User login Activity

Description:

The user enters a user name and password. If the user name and password is verified then the user login
is successful and user is redirected to the home-page. If the login is not successful then the user can either enter
his password and user name (the user can do this for only a maximum of 3times) or he can click on forgot
username/password. Then a security question is asked. If that is verified, then an email is sent on the user's
mail id else the request is forwarded to the admin.

21
 3.6.3Managing Accounts Activity

Fig 3.6.3 Managing Accounts Activity

Description:

An activity diagram visually presents a series of actions or flow of control in a system similar to a
flowchart or a data flow diagram. Activity diagrams are often used in business process modeling In both cases
an activity diagram will have a beginning (an initial state) and an end (a final state).

 Aregistereduser(admin,moderator,alumni,faculty,student)canmanagetheir accounts by doing the following

 Change password
 Delete account
 Edit details

22
3.6.4 Rate and comment activity

Fig 3.6.4 Rate and comment activity

Description:

If a user is a registered user then he can comment or rate an article but if it is guest then he cannot rate
or comment an article. This shows that an alumni will not be comment or rate on an article

3.6.5 Report Comment Activity

Fig 3.6.5 Report Comment Activity

Description:

If the user is a registered user then he can report a comment. Then a notice is forwarded to
moderator to report the comment. The moderator can either remove the comment or ignore the
request to report that comment. Incase the user Is a guest then he cannot report a comment.

23
3.6.6 Registration Activity

Fig 3.6.6 Registration Activity

Desciption:

Initially student/faculty is made to fill mandatory fields filled in registration form. once the user click
submit, the details are verified. If the details are incomplete then the user is in formed to fill the complete
details and is redirected to the page Where the details have to be filled. If the details that are filled are complete
then it is checked whether it is a new user or already existing user fit is an already existing user then the user
Is asked to renter the details. If it is a new user then the user will create a user name and a password. Then if it is
a valid user name and password then he/she is registered and is redirected to the home-page. If it is an invalid
and password then the user is made to renter his/her username and password.

24
 3.6.7 Submit Article Activity

Fig 3.6.7 Submit Article Activity

Description:

 If a user intends to post an article then he creates article and submits it in the appropriate category. The article
is then received by them or of that particular category in which the article has been added. The moderator can
Reject the article if he founds some un acceptable stuff in it He can simply approve the article he can put the
article in a different category if he feels the article is not a perfect for the category it was submitted for. Then
this is verified by the user who submitted

 The article. The user can either verify the category change or submit the article or he does not verify the
category change and with draws the article.

25
Chapter 4

LANGUAGE IMPLEMENTATION AND RESULT

A TEST CASE is a set of conditions or variables under which a tester will determine whether a system
under test satisfies requirements or works correctly. The process of developing test cases can also help find
problems in the requirements or design of an application.

 The visitor’s web browser requests the web page using a standard URL.
 The web server software (typically Apache) recognizes that the requested file is a PHP script, so the
server fires up the PHP interpreter to execute the code contained in the file.
 Certain PHP commands (which will be the focus of this chapter) connect to the MySQL database and
request the content that belongs in the web page.
 The MySQL database responds by sending the requested content to the PHP script.
 The PHP script stores the content into one or more PHP variables, then uses echo statements to output
the content as part of the web page.
 The PHP interpreter finishes up by handing a copy of the HTML it has created to the web server.
 The web server sends the HTML to the web browser as it would a plain HTML file, except that instead
of coming directly from an HTML file, the page is the output provided by the PHP interpreter.
Connecting to MySQL with PHP Before you can retrieve content out of your MySQL database for
inclusion in a web page, you must know how to establish a connection to MySQL from inside a PHP
script. Back in Introducing MySQL, you used a program called mysql that allowed you to make such
a connection from the command prompt. Just as that program could connect directly to a running
MySQL server, so too can the PHP interpreter; support for connecting to MySQL is built right into the
language in the form of a library of built-in functions. Introducing PHP that PHP functions usually
return a value when they’re called. The mysqli_connect function, for example, returns a link identifier
that identifies the connection that has been established. Since we intend to make use of the connection,
we should hold onto this value. Here’s how we might connect to our MySQL server: example of As
described above, the values of the three function parameters may differ for your MySQL server; at the
very least, you’ll need to substitute in the root password you established for your MySQL server.
What’s important to see here is that the value returned by mysqli_connect is stored in a variable
named $link.As the MySQL server is a completely separate piece of software from the web server, we
must consider the possibility that the server may be unavailable or inaccessible due to a network outage,
or because the username/password combination you provided is rejected by the server. In such cases,
the mysqli_connect function returns FALSE, instead of a connection identifier, as no connection is
established. This allows us to react to such failures using an if statement:

26
4.1 Database Design:
How to Write Test Cases: Sample Template with Examples
What is a Test Case?
A Test Case is defined as a set of actions executed to verify a particular feature or functionality of the software
application. A test case is an indispensable component of the Software Testing Life Cycle that helps validate
the AUT (Application under Test).
Test Scenario Verses Test Case
Test scenarios are rather vague and cover a wide range of possibilities. Testing is all about being very specific.
For a Test Scenario: Check Login Functionality there many possible test cases are:
Test Case 1: Check results on entering valid User Id & Password
Test Case 2: Check results on entering Invalid User ID & Password
Test Case 3: Check response when a User ID is Empty & Login Button is pressed, and many more
This is nothing but a Test Case

4.2 Database Tables

4.2.1 Login table

Login

Field Name DataType Size Key Description

Username Varchar 20 Primary key User name

Password Varchar 20 password

4.2.2 User table

users

27
 Field Name DataType Size Key Description

id varchar 20 Name

username varchar 20 name

Firstname Varchar 100 name

Lastname Varchar 20 name

email Varchar 30 Primary key email

password varchar 20 password

4.2.3 Posts table

Posts

DataType Size Key

id int 10 Primary Key

Title char 50
Author char 50

Postdate varchar 20
Image clob
Content varchar 150
Update_on date
status varchar 20
tag varchar

28
Chapter 5
TEST-CASE RESULT

A Test Case is defined as a set of actions executed to verify a particular feature or functionality of the
software application. A test case is an indispensable component of the Software Testing Life-Cycle that helps
validate the AUT (Application under Test).
Test Scenario Verses Test Case
Test scenarios are rather vague and cover a wide range of possibilities. Testing is all about being very specific.
For a Test Scenario: Check Login Functionality there many possible test cases are:
Test Case 1: Check results on entering valid User Id & Password
Test Case 2: Check results on entering Invalid User ID & Password
Test Case 3: Check response when a User ID is Empty & Login Button is pressed.

Step 1) A simple test case for the scenario would be

Test Case # Test Case Description

1 Check response when valid email and password is entered

Step 2) In order to execute the test case, you would need Test Data. Adding it below
Test Test Case Description Test Data
Case #
1 Check response when valid email and Email: ####@email.com Password: lNf9^Oti7^2h
password is entered

Identifying test data can be time-consuming and may sometimes require creating test data afresh. The reason
it needs to be documented.
Step 3) In order to execute a test case, a tester needs to perform a specific set of actions on the AUT. This is
documented as below:

Test Test Case Description Test Steps Test Data

Case #

29
 1 Check response when valid email and 1) Enter Email Email:####@email.com
password is entered Address Password: lNf9^Oti7^2h
2) Enter
Password
3) Click Sign in

Many times the Test Steps are not simple as above, hence they need documentation. Also, the author of the
test case may leave the organization or go on a vacation or is sick and off duty or is very busy with other
critical tasks. A recently hire may be asked to execute the test case. Documented steps will help him and also
facilitate reviews by other stakeholders.

Step 4) The goal of test cases is to check behaviour the AUT for an expected result. This needs to be
documented as below

Test Test Case Description Test Data Expected Result

Case #

1 Check response when valid email Email: ####@email.com Login should be successful
and password is entered Password: lNf9^Oti7^2h

During test execution time, the tester will check expected results against actual results and assign a pass or fail
status

Test Test Case Test Data Expected Actual Pass/Fail

Case Description Result Result
#
1 Check Email: ####@email.com Password: Login Login Pass
response lNf9^Oti7^2h should be was
when valid successful successful
email and
password is
entered

30
 Step 5) That apart your test case -may have a field like, Pre - Condition which specifies things that must in
place before the test can run. For our test case, a pre-condition would be to have a browser installed to have
access to the site under test. A test case may also include Post- Conditions which specifies anything that applies
after the test case completes. For our test case, a post condition would be time & date of login is stored in the
database

5.1 Login Test-cases

Test Case ID 1 Test Case Description Test the login functionality in magazine
Created By pradeep Reviewed By sajjad Version 2.1

Tester's Name sajjad and Date Tested September 8, 2019 Test Case Pass
pradeep (Pass/Fail/Not
Executed)

S# Prerequisites: S# Test Data

1 Access to Chrome Browser 1 Userid = superadmin
2 2 Pass = superadmin
3 3
4 4

Test Verify on entering valid userid and password, the customer can
Scenario login

Step # Step Details Expected Results Actual Results Pass / Fail / Not executed /
Suspended

1 Navigate to homepage window homepage pass

localhost/demo9
2 Enter Userid& Credential can be As Expected Pass
Password entered
3 Click Submit Cutomer is logged in As Expected Pass
4

5.2 Posts test-cases

Test Case ID 1 Test Case Test the post functionality in posts section
Description
Created By pradeep Reviewed By sajjad Version 2.1

31
Tester's Name sajjad and pradeep Date Tested October 8, 2019 Test Case Pass
(Pass/Fail/Not
Executed)

S# Prerequisites: S# Test Data

1 Access to Chrome Browser 1 Userid = superadmin

2 2 Pass = superadmin

3 3

4 4

Test Verify on entering valid userid and password, the customer can
Scenario login

Step # Step Details Expected Results Actual Results Pass / Fail / Not executed /
Suspended

1 Navigate to localhost/demo9/posts posts window posts window pass

2 Enter project desciption and title and posts shown on post posts shown on post window Pass
upload image window
3 Click Submit post displayed As Expected Pass

32
 CONCLUSION

An online magazine stocks some functions with a blog and also with internet magazines, but can
usually be recognized by its approach to article management. Publications normally have publishers or article
forums who review distribution and perform a function to ensure that all material satisfies the objectives of
the marketers (those investing time or money in its production) and the audience. The College Magazine where
college students and faculties can post and read various articles, thus promoting. Articles can be searched by
anybody in the world. Factors behind the motivation of this system. In this all students not make it to the
printed magazine. Creativity of student needs to be nurtured and creating a user-friendly interactive place
where students/faculties can share their ideas.

33
 REFERENCES

[1] Author, A. A., & Author, B. B. (Date of publication). Title of article. In Title of book or larger document
(chapter or section number). Retrieved from https://www.someaddress.com /full/url/

[2] Peckinpaugh, J. (2003). Change in the Nineties. In J. S. Bough and G. B. DuBois (Eds.), A century of
growth in America. Retrieved from GoldStar database.

[3] De Huff, E. W. (n.d.). Taytay’s tales: Traditional Pueblo Indian tales. Retrieved from
https://digital.library.upenn.edu/women/deh uff/taytay/taytay.html International Journal of Management,
Technology And Engineering Volume IX, Issue II, FEBRUARY/2019 ISSN NO : 2249-7455 Page No: 1315

[4] Davis, J. (n.d.). Familiar birdsongs of the Northwest. Available from https://www.powells. com/cgi-
bin/biblio? inkey=1-9780931686108-0

34