BIJIT

PROBLEM STATEMENT
BVICAM’s International Journal of Information Technology (BIJIT) publishes research papers

related to various areas of Information Technology. BIJIT Editorial Board (BEB) sends
invitation to authors for submission of papers through mails and website. Author submits the
manuscript, through mail, as per the Guidelines for Authors, available at website. BEB send the
submission confirmation to the Authors via mail after allocating a Manuscript ID. Authors are
required to use the allotted ID for further correspondence. Internal reviewers review the new
submitted manuscripts. The manuscript that fulfills the basic standards, are accepted for the
external review process. BEB selects a reviewer from the existing database, based on the
research area of the reviewer; to send the review request via mail. After acceptance of the request
the BEB send the manuscript for the blind review to the reviewer with review form via mail.
External reviewer with detailed feedback can recommend the paper to Accept as it is/ minor
revision/major revision and clear reject. The authors are requested to submit the revised
manuscript with compliance report in case of Minor Revision and Major Revision. BEB is facing
several problems in this manual system to track the status information of the submitted
manuscripts. BEB wants a web based solution which provides the automation from submission
of new manuscript till acceptance or rejection of the submitted manuscript.
USE CASE DIAGRAM
User Registration
(from User Registration)
<<extend>>
User Register as author or

Login reviewer
(from Actors) (from Register as author or reviewer)
(from Login)
<<extend>>
Internal Feedback Change password

(from Internal Feedback) (from Change Password)
<<include>>
Assign IR
(from Assign IR)
<<include>>
Internal
Reviewer BEB
(from Actors) <<include>> Select Reviewer
Confirm for Review (from Actors)
(from Select Reviewer)
(from Confirm for Review)
<<include>>
External
Reviewer Assign ER
(from Actors) (from Assign ER)
Author
(from Actors)
External Feedback
(from External Feedback)
Submit Manuscript
(from Submit Manuscript)
Send Revise Manuscript

(from Revise Manuscript)
Track Status
(from Track Status)
Float Invitation
(from Float Invitation)
USE-CASE SPECIFICATION- USER REGISTRATION
Project Name : BIJIT
Use case ID : BIJIT_001
Use case Name : User Registration
Brief Description : This is a use case for registration of a user.
Primary Actors : Users
Secondary Actors : None
Pre conditions: None
Main Flow:
1. Select user registration option.
2. System will display user registration form.
3. User will enter username.
4. System will check the validity.
5. If valid enter email id and password else goto step 3
6. System will check email id and password
7. If selected as reviewer or author then extend use case “Register as author or reviewer”.
8. Select submit
9. System will store data
10. System will generate confirmation mail and notification mail
11. System will send confirmation mail to user
12. System will send notification mail to BEB.
Post Conditions : 1. User should receive the confirmation mail.

2. BEB should receive the notification mail.
Alternative Flow : None

ACTIVITY DIAGRAM- USER REGISTRATION
User System
select user
registration option
display user
registration form
enter user
name check validity
Not Valid
Valid
enter email id and
password
No if user register as
author or reviewer
Enter specific user

information
select submit store

information
generate generate
confirmation mail notification mail
USE-CASE SPECIFICATION-LOGIN
Use case Name : Login
Brief Description : This is a use case for logging in of a user.
Primary Actors : BEB & Users
Pre conditions:
1. Authors, reviewers and subscribers should be registered users of BIJIT.
Main Flow:
1. User will enter username and password.
2. System will check the validity.
2.1 If it is valid , it will display the user type.
2.2 If it is not valid go to step 1.
Post Conditions : Based upon the user type it will display the user information.

ACTIVITY DIAGRAM-LOGIN
User System
Enter user name Check Validity

and password
Invalid
Valid
Display user type

and information
USE-CASE SPECIFICATION-SUBMIT MANUSCRIPT
Use case Name : Submit Manuscript
Brief Description : This is a use case for submitting research paper by author
Primary Actors : Author and System
Pre conditions:
1. User should login as Author
Main Flow:
1. Select submit manuscript option.

2. System will display a blank wordpad file connected to MS OUTLOOK.
3. Author will copy manuscript on that wordpad.
4. Author click submit button.
5. System will display message “Submission done”
6. System will send the manuscript to BEB.
7. System will send submit_notification mail to BEB and author.
Post Conditions : 1. BEB should receive the manuscript.
2. Author and BEB should receive the notification mail.

ACTIVITY DIAGRAM-SUBMIT MANUSCRIPT
Author System
Select submit Display a blank wordpad file

manuscript option connected to MS OUTLOOK
copy manuscript
on wordpad
click submit display message

button "Submission done"
send the manuscript

to BEB
send submit_notification
mail to BEB
send submit_notification
mail to Author
USE-CASE SPECIFICATION-ASSIGN IR
Use case Name : Assign IR
Brief Description : This is a use case for assigning internal reviewer
Primary Actors : BEB & Internal reviewer
Pre conditions:
Login as BEB
Main Flow:
1. System checks the research area of manuscript.

2. System finds internal reviewers with same research area from internal reviewer database.
3. BEB Allocates an internal reviewer from this list randomly.
4. Sends manuscript to that reviewer.
5. Sends send_notification mail to internal reviewer.
Post Conditions : Selected internal reviewer should receive manuscript and send_notification
mail

ACTIVITY DIAGRAM-ASSIGN IR
System BEB
Checks the research

area of manuscript
Finds internal reviewers with same research Allocates an internal reviewer

area from internal reviewer database from this list randomly
Sends manuscript to that

reviewer
Sends send_notification mail to

internal reviewer
USE-CASE SPECIFICATION- INTERNAL FEEDBACK
Use case Name : Internal Feedback
Brief Description : This is a use case for giving internal feedback
Primary Actors : BEB ,Internal reviewer
Pre conditions:
Login as Internal reviewer
Main Flow:
1. Internal Reviewer reads the manuscript.

2. Internal Reviewer checks whether it is meeting basic standards or not.
2.1 If it is meeting basic standards
2.1.1 Send acceptance_mail to BEB.
2.1.2 BEB enter manuscript id for further external review process in the internal
acceptance database
2.2 If it is not meeting basic standards
2.2.1 Send rejection_mail to BEB
2.2.2 BEB enter manuscript ID in the rejection database.
2.2.3 System sends rejection_mail to corresponding author.
Post Conditions : BEB should receive either acceptance_mail or rejection_mail

ACTIVITY DIAGRAM- INTERNAL FEEDBACK
Intern al Reviewer BEB S YS T EM
Reads the
manuscript
Checks whether it is meeting

basic standards or not
No
Yes
Send acceptance_mail to Enter manuscript id for further external review
BEB process in the internal acceptance database
Send rejection_mail Enter manuscript ID in Sends rejection_mail to

to BEB the rejection database corresponding author
USE-CASE SPECIFICATION- ASSIGN ER
Use case Name : Assign ER
Brief Description : This is a use case for assigning external reviewer
Primary Actors : BEB & External reviewer
Pre conditions:
Login as BEB
Main Flow:
1. System checks the research area of manuscript.

2. System finds external reviewers with same research area from external reviewer database.
3. BEB selects an external reviewer from this list.
4. System Sends request mail to that reviewer.
5. External reviewer gets the request mail.
6. If External Reviewer accepts the request
6.1 BEB send the manuscript for the blind review to the reviewer with review form via
mail
7. If External Reviewer does not accepts the request
7.1 BEB selects another reviewer from the list
7.2 Go to step 4 and process is repeated.
Post Conditions : Selected external reviewer should receive manuscript.

ACTIVITY DIAGRAM-ASSIGN ER
System BEB Ex ternal Reviewer
Checks the research

area of manuscript.
Finds external reviewers with same research Selects an external

area from external reviewer database reviewer from this list
Gets the
Sends request mail to request mail
that reviewer
Sends the manuscript with review form accepts

to external reviewer via mail
Selects another not accepted

reviewer from the list
USE-CASE SPECIFICATION- EXTERNAL FEEDBACK
Use case Name : External Feedback
Brief Description : This is a use case for giving external feedback
Primary Actors : BEB ,External reviewer
Pre conditions:
Login as Internal reviewer
Main Flow:
1. External Reviewer reads the manuscript.

2. External Reviewer recommend paper and send recommendation mail to BEB
2.1. if recommend as accept as it is
2.1.1. BEB sends acceptance_mail to the author.
2.1.2. BEB sends manuscript for publishing in BIJIT magazine
2.2. if recommend minor revision/major revision
2.2.1. BEB sends that mail to the author.
2.2.2. BEB Stores that id in further_judgement database
2.3. if recommend as clear reject
2.3.1. BEB enter manuscript ID in the rejection database.
2.3.2. System sends rejection_mail to corresponding author
Post Conditions : 1. BEB should receive the recommendation mail.
2.Author should receive the feedback_mail

ACTIVITY DIAGRAM- EXTERNAL FEEDBACK
Ex ternal Reviewer BEB System
Reads the
manuscript
Recommend paper and send

recommendation mail to BEB Sends acceptance_mail
to the author.
Accept as it is
Sends manuscript for publishing
in BIJIT magazine
major/minor
revision BEB sends that mail to
the author.
Stores that id in
further_judgement database
Sends rejection_mail to
Clear reject Enter manuscript ID in the corresponding author
rejection database
USE-CASE SPECIFICATION-SUBMIT REVISED MANUSCRIPT
Use case Name : Submit revised manuscript
Brief Description : This is a use case for sending revised manuscript
Primary Actors : Author
Pre conditions:
2. Login as Author
Main Flow:
1. Author will enter manuscript_ID

2. System checks whether ID is stored in further_judgement database or not
3. If it is present
3.1 System will display a blank wordpad file connected to MS OUTLOOK
3.2 Author will copy manuscript on that wordpad.
3.3 Author click submit button.
3.4 System will display message “Resubmission done”
3.5 System will send the manuscript to BEB.
3.6 System will send notification mail to BEB and author.
4. if it is not present
4.1 System will display message “ You don’t have to submit revised manuscript”
Post Conditions : None

ACTIVITY DIAGRAM- SUBMIT REVISED MANUSCRIPT
Author System
Checks whether ID is stored in

Enter
further_judgement database or not
manuscript ID
no
yes
Copy manuscript on Display a blank wordpad file

that wordpad connected to MS OUTLOOK
Click submit Display message

button "Resubmission done"
Send the manuscript

to BEB
Send notification mail to

BEB and author
Display message " You don't have to

submit revised manuscript"
USE-CASE SPECIFICATION-TRACK STATUS
Use case Name : Track Status
Brief Description : This is a use case for tracking the status of the manuscript
Primary Actors : User and BEB
Pre conditions:
3. Should login as user or BEB
Main Flow:
1. Enter the id of manuscript.

2. System will display status of manuscript as accepted and gone for publishing or
further_judgement required or rejected.
Post Conditions : None

ACTIVITY DIAGRAM-TRACK STATUS
User or BEB System
Enter the id of Display status of manuscript as accepted and gone for

manuscript publishing or further_judgement required or rejected
USE-CASE SPECIFICATION-FLOAT INVITATION
Use case Name : Float Invitation
Brief Description : This is a use case for sending invitations to authors for submission of papers
through mails and website
Primary Actors : BEB
Pre conditions:
Login as BEB
Main Flow:
1. BEB will check the database of existing users.
2. BEB will click send invitation button.
3. System will send invitation_mail to all the e-mail id’s in that database.
4. System will also display invitation on the website.
Post Conditions : Existing users should receive invitation mails

ACTIVITY DIAGRAM-FLOAT INVITATION
BEB S ystem
check the database

of existing users
click send send invitation_mail to all the

invitation button e-mail id's in that database
display invitation on
the website
ANALYSIS MODEL
User resgistration form User data
validation
Login form notification mail
confirmation mail
acceptance_mail
submission interface rejection_mail
submit_notification mail
internal reviewer selector internal_reviewer

submission controller database
resubmission mail
selection controller
external reviewer selector
external reviewer
invitation panel database
user database
external feedback interface request form

internal feedback interface
invitation mail
status displayer
further judgement
database
SEQUENCE DIAGRAM- USER REGISTRATION
: User : User resgistration form : User data : validation
1: select user registration
2: display(form)
3: put_data(username)
4: store_data(username)
5: put_data(email_id, password)
6: check_data(user_id,password)
7: save(user_id, password)
8: send notification mail
SEQUENCE DIAGRAM- LOGIN
: User : Login form : validation : User data

1: click
2: put_data(id,password)
3: validate_data(id,password)
4: check
5: valid
6: display user type

SEQUENCE DIAGRAM- SUBMIT MANUSCRIPT
: submission controller : submit_notification

: submission interface
mail
1: select option
2: put (wordpad file)

3: submit(manuscript)
4: submission done
5: send(mail)
SEQUENCE DIAGRAM- ASSIGN IR
: Internal : BEB : internal reviewer selector: internal_reviewer: selection controller

Reviewer 1: check(research area) database
2: find(research area)
3: select
4: send(manuscript)
5: send(send_notification mail)
SEQUENCE DIAGRAM- INTERNAL FEEDBACK
: Internal : BEB send(mail) : internal feedback: acceptance_mail: rejection_mail

Reviewer interface
1: match(manuscript,standard_manuscript)
2: send(mail)
3: deposit(manuscript)
4: send(mail)
5: reject(manuscript)
SEQUENCE DIAGRAM- ASSIGN ER
: External : selection controller

: BEB : external feedback interface : external reviewer
Reviewer
database
1: search(research_area)
2: select(research_area)
3: select
4: send(request_mail)
5: accept
6: send(manuscript)
SEQUENCE DIAGRAM- EXTERNAL FEEDBACK
: External : BEB : external feedback interface : further judgement

Reviewer database
1: recommend(mail)
2: accept(manuscript)
3: send(acceptance_mail)
4: revision required
5: store(manuscript_id)
6: send(revision_required mail)
7: rejection
8: send(rejection_mail)
SEQUENCE DIAGRAM- SUBMIT REVISED MANUSCRIPT
: submission interface : submission controller : submit_notification

mail
1: select option
2: put (wordpad file)

3: submit(manuscript)
4: resubmission done
5: send(mail)
SEQUENCE DIAGRAM- TRACK STATUS
: User : BEB : status displayer

1: show_status(manuscript_id)
2: status
3: show_status(manuscript_id)
4: status
SEQUENCE DIAGRAM- FLOAT INVITATION
: BEB : invitation panel : user database : invitation mail
1: check
2: click send_invitation button

3: put_data(email_id)
4: invitation send
User data
User registration form login_id
password
select() user_name
put_data() email_id
Invitation panel
check()
Validation send_invitation()
store_data()
Login form
save()
login_id validate_data()
password check_data()
Notification mail User database
click()
put_data() send() check()
Confirmation mail
send()
Submission interface Invitation mail

Submit_notification mail
Status displayer email_id
select() send() status
manuscript_id put_data()
Resubmission mail show_status()

Submission controller
manuscript send()
email_id
Rejection mail
submit()
resubmition() email_id
Acceptance mail send()

Internal reviewer selector email_id
Internal reviewer database
send()
check() research_area
manuscript
standard_manuscript
Selection controller
External reviewer selector manuscript_id
select() find()
check()
External reviewer database

External feedback interface research_area
search() select()
accept()
revision_required()
rejection() Internal feedback interface
match()
deposite()
Further judgement database reject()
manuscript_id
store()
FORWARD ENGINEERING- CODE GENERATION
CPP FILES
#include "Acceptance mail.h"
//##ModelId=4CF2AB5900DA
Acceptance mail::send()
{
}
#include "Confirmation mail.h"
//##ModelId=4CF2AE8C02DE
Confirmation mail::send()
{
}
#include "External feedback interface.h"
//##ModelId=4CF2A8A403D8
External feedback interface::search(void research_area)
{
}
//##ModelId=4CF2A9650261
External feedback interface::accept()
{
}
//##ModelId=4CF2AA4F03D8
External feedback interface::revision_required()
{
}
//##ModelId=4CF2AA8A0157
External feedback interface::rejection()
{
}
#include "External reviewer database.h"
//##ModelId=4CF2A91103A9
External reviewer database::select(void research_arae)
{
}
#include "External reviewer selector.h"
//##ModelId=4CF2AEF30157
External reviewer selector::check()
{
}
#include "Further judgement database.h"
//##ModelId=4CF2AA65007D
Further judgement database::store(void manuscript_id)
{
}
#include "Internal feedback interface.h"
//##ModelId=4CF2AB020222
Internal feedback interface::match(void manuscript, void standard_manuscript)
{
}
//##ModelId=4CF2ABB100AB
Internal feedback interface::deposite()
{
}
//##ModelId=4CF2ABDC0242
Internal feedback interface::reject()
{
}
#include "Internal reviewer database.h"
//##ModelId=4CF2A9C60196
Internal reviewer database::find(void research_area)
{
}
#include "Internal reviewer selector.h"
//##ModelId=4CF2A9AF003E
Internal reviewer selector::check(void research_area)
{
}
#include "Invitation mail.h"
//##ModelId=4CF2AAC9034B
Invitation mail::put_data()
{
}
#include "Invitation panel.h"
//##ModelId=4CF2AAB902FD
Invitation panel::send_invitation()
{
}
#include "Login form.h"
//##ModelId=4CF2ABF6030D
Login form::click()
{
}
//##ModelId=4CF2ABFF03A9
Login form::put_data(void login_id)
{
}
#include "Notification mail.h"
//##ModelId=4CF2AE9903C8
Notification mail::send()
{
}
#include "Rejection mail.h"
//##ModelId=4CF2ABBD02EE
Rejection mail::send()
{
}
#include "Resubmission mail.h"
//##ModelId=4CF2AD390177
Resubmission mail::send(void email_id)
{
}
#include "Selection controller.h"
Selection controller::select()
{
}
#include "Status displayer.h"

//##ModelId=4CF2AD88002E
Status displayer::show_status()
{
}
#include "Submission controller.h"
//##ModelId=4CF2ACC60167
Submission controller::submit(void manuscript)
{
}
//##ModelId=4CF2ACF6007D
Submission controller::resubmition()
{
}
#include "Submission interface.h"
//##ModelId=4CF2ACAF01A5
Submission interface::select(void option)
{
}
#include "Submit_notification mail.h"
//##ModelId=4CF2AD2902AF
Submit_notification mail::send(void email_id)
{
}
#include "User data.h"
//##ModelId=4CF2AC3900EA
User data::check()
{
}
//##ModelId=4CF2AE2A03A9
User data::store_data()
{
}
User data::save()
{
}
#include "User database.h"

//##ModelId=4CF2AAA701C5
User database::check()
{
}
#include "User registration form.h"
//##ModelId=4CF2AE080271
User registration form::select()
{
}
//##ModelId=4CF2AE14008C
User registration form::put_data()
{
}
#include "Validation.h"
//##ModelId=4CF2AC2B008C
Validation::validate_data()
{
}
//##ModelId=4CF2AE6A02AF
Validation::check_data()
{
}
HEADER FILES
Header files
#ifndef ACCEPTANCE_MAIL_H_HEADER_INCLUDED_B30D7235
#define ACCEPTANCE_MAIL_H_HEADER_INCLUDED_B30D7235
//##ModelId=4CF283020048
class Acceptance mail
{
public:
//##ModelId=4CF2AB5900DA
send();
private:
email_id;
};
#endif /* ACCEPTANCE_MAIL_H_HEADER_INCLUDED_B30D7235 */
#ifndef CONFIRMATION_MAIL_H_HEADER_INCLUDED_B30D0AD2
#define CONFIRMATION_MAIL_H_HEADER_INCLUDED_B30D0AD2
//##ModelId=4CF283DF01DE
class Confirmation mail
{
public:
//##ModelId=4CF2AE8C02DE
send();
};
#endif /* CONFIRMATION_MAIL_H_HEADER_INCLUDED_B30D0AD2 */
#ifndef EXTERNAL_FEEDBACK_INTERFACE_H_HEADER_INCLUDED_B30D1CB4
#define EXTERNAL_FEEDBACK_INTERFACE_H_HEADER_INCLUDED_B30D1CB4
//##ModelId=4CF282C80096
class External feedback interface
{
public:
//##ModelId=4CF2A8A403D8
search(void research_area);
accept();
//##ModelId=4CF2AA4F03D8
revision_required();
//##ModelId=4CF2AA8A0157
rejection();
};
#endif /* EXTERNAL_FEEDBACK_INTERFACE_H_HEADER_INCLUDED_B30D1CB4 */
#ifndef EXTERNAL_REVIEWER_DATABASE_H_HEADER_INCLUDED_B30D708A
#define EXTERNAL_REVIEWER_DATABASE_H_HEADER_INCLUDED_B30D708A
//##ModelId=4CF282980307
class External reviewer database
{
public:
//##ModelId=4CF2A91103A9
select(void research_arae);
private:
research_area;
};
#endif /* EXTERNAL_REVIEWER_DATABASE_H_HEADER_INCLUDED_B30D708A */
#ifndef EXTERNAL_REVIEWER_SELECTOR_H_HEADER_INCLUDED_B30D7243
#define EXTERNAL_REVIEWER_SELECTOR_H_HEADER_INCLUDED_B30D7243
//##ModelId=4CF282870104
class External reviewer selector
{
public:
//##ModelId=4CF2AEF30157
check();
};
#endif /* EXTERNAL_REVIEWER_SELECTOR_H_HEADER_INCLUDED_B30D7243 */
#ifndef FURTHER_JUDGEMENT_DATABASE_H_HEADER_INCLUDED_B30D19D7
#define FURTHER_JUDGEMENT_DATABASE_H_HEADER_INCLUDED_B30D19D7
//##ModelId=4CF282740327
class Further judgement database
{
public:
//##ModelId=4CF2AA65007D
store(void manuscript_id);
private:
//##ModelId=4CF2AA760186
manuscript_id;
};
#endif /* FURTHER_JUDGEMENT_DATABASE_H_HEADER_INCLUDED_B30D19D7 */
#ifndef INTERNAL_FEEDBACK_INTERFACE_H_HEADER_INCLUDED_B30D5489
#define INTERNAL_FEEDBACK_INTERFACE_H_HEADER_INCLUDED_B30D5489
//##ModelId=4CF2826103C3
class Internal feedback interface
{
public:
match(void manuscript, void standard_manuscript);
//##ModelId=4CF2ABB100AB
deposite();
//##ModelId=4CF2ABDC0242
reject();
};
#endif /* INTERNAL_FEEDBACK_INTERFACE_H_HEADER_INCLUDED_B30D5489 */
#ifndef INTERNAL_REVIEWER_DATABASE_H_HEADER_INCLUDED_B30D46A3
#define INTERNAL_REVIEWER_DATABASE_H_HEADER_INCLUDED_B30D46A3
//##ModelId=4CF2822F01CF
class Internal reviewer database
{
public:
find(void research_area);
private:
//##ModelId=4CF2A9DE01C5
research_area;
//##ModelId=4CF2AB3800CB
manuscript;
standard_manuscript;
//##ModelId=4CF2ADC6000F
manuscript_id;
};
#endif /* INTERNAL_REVIEWER_DATABASE_H_HEADER_INCLUDED_B30D46A3 */
#ifndef INTERNAL_REVIEWER_SELECTOR_H_HEADER_INCLUDED_B30D7608
#define INTERNAL_REVIEWER_SELECTOR_H_HEADER_INCLUDED_B30D7608
//##ModelId=4CF2824902F8
class Internal reviewer selector
{
public:
//##ModelId=4CF2A9AF003E
check(void research_area);
};
#endif /* INTERNAL_REVIEWER_SELECTOR_H_HEADER_INCLUDED_B30D7608 */
#ifndef INVITATION_MAIL_H_HEADER_INCLUDED_B30D3D4B
#define INVITATION_MAIL_H_HEADER_INCLUDED_B30D3D4B
//##ModelId=4CF282220067
class Invitation mail
{
public:
//##ModelId=4CF2AAC9034B
put_data();
private:
//##ModelId=4CF2AAD200FA
email_id;
};
#endif /* INVITATION_MAIL_H_HEADER_INCLUDED_B30D3D4B */
#ifndef INVITATION_PANEL_H_HEADER_INCLUDED_B30D2A41
#define INVITATION_PANEL_H_HEADER_INCLUDED_B30D2A41
//##ModelId=4CF28216027B
class Invitation panel
{
public:
//##ModelId=4CF2AAB902FD
send_invitation();
};
#endif /* INVITATION_PANEL_H_HEADER_INCLUDED_B30D2A41 */
#ifndef LOGIN_FORM_H_HEADER_INCLUDED_B30D37E4
#define LOGIN_FORM_H_HEADER_INCLUDED_B30D37E4
class Login form
{
public:
//##ModelId=4CF2ABF6030D
click();
//##ModelId=4CF2ABFF03A9
put_data(void login_id);
private:
//##ModelId=4CF2AC86036B
login_id;
//##ModelId=4CF2AC8D01C5
password;
};
#endif /* LOGIN_FORM_H_HEADER_INCLUDED_B30D37E4 */
#ifndef NOTIFICATION_MAIL_H_HEADER_INCLUDED_B30D3777
#define NOTIFICATION_MAIL_H_HEADER_INCLUDED_B30D3777
//##ModelId=4CF281F700B6
class Notification mail
{
public:
send();
};
#endif /* NOTIFICATION_MAIL_H_HEADER_INCLUDED_B30D3777 */
#ifndef REJECTION_MAIL_H_HEADER_INCLUDED_B30D05D2
#define REJECTION_MAIL_H_HEADER_INCLUDED_B30D05D2
//##ModelId=4CF281EC01CF
class Rejection mail
{
public:
//##ModelId=4CF2ABBD02EE
send();
private:
//##ModelId=4CF2ABC200BB
email_id;
};
#endif /* REJECTION_MAIL_H_HEADER_INCLUDED_B30D05D2 */
#ifndef RESUBMISSION_MAIL_H_HEADER_INCLUDED_B30D500F
#define RESUBMISSION_MAIL_H_HEADER_INCLUDED_B30D500F
//##ModelId=4CF281D101A0
class Resubmission mail
{
public:
//##ModelId=4CF2AD390177
send(void email_id);
};
#endif /* RESUBMISSION_MAIL_H_HEADER_INCLUDED_B30D500F */
#ifndef SELECTION_CONTROLLER_H_HEADER_INCLUDED_B30D683F
#define SELECTION_CONTROLLER_H_HEADER_INCLUDED_B30D683F
//##ModelId=4CF281C6028A
class Selection controller
{
public:
select();
};
#endif /* SELECTION_CONTROLLER_H_HEADER_INCLUDED_B30D683F */
#ifndef STATUS_DISPLAYER_H_HEADER_INCLUDED_B30D320A
#define STATUS_DISPLAYER_H_HEADER_INCLUDED_B30D320A
//##ModelId=4CF281B70346
class Status displayer
{
public:
//##ModelId=4CF2AD88002E
show_status();
private:
//##ModelId=4CF2ADE30177
status;
//##ModelId=4CF2ADEF02DE
manuscript_id;
};
#endif /* STATUS_DISPLAYER_H_HEADER_INCLUDED_B30D320A */
#ifndef SUBMISSION_CONTROLLER_H_HEADER_INCLUDED_B30D00FE
#define SUBMISSION_CONTROLLER_H_HEADER_INCLUDED_B30D00FE
//##ModelId=4CF2844B0029
class Submission controller
{
public:
//##ModelId=4CF2ACC60167
submit(void manuscript);
//##ModelId=4CF2ACF6007D
resubmition();
private:
//##ModelId=4CF2AD0103A9
manuscript;
//##ModelId=4CF2AD4700AB
email_id;
};
#endif /* SUBMISSION_CONTROLLER_H_HEADER_INCLUDED_B30D00FE */
#ifndef SUBMISSION_INTERFACE_H_HEADER_INCLUDED_B30D39BC
#define SUBMISSION_INTERFACE_H_HEADER_INCLUDED_B30D39BC
class Submission interface
{
public:
//##ModelId=4CF2ACAF01A5
select(void option);
};
#endif /* SUBMISSION_INTERFACE_H_HEADER_INCLUDED_B30D39BC */
#ifndef SUBMIT_NOTIFICATION_MAIL_H_HEADER_INCLUDED_B30D3A64
#define SUBMIT_NOTIFICATION_MAIL_H_HEADER_INCLUDED_B30D3A64
//##ModelId=4CF281930307
class Submit_notification mail
{
public:
//##ModelId=4CF2AD2902AF
send(void email_id);
};
#endif /* SUBMIT_NOTIFICATION_MAIL_H_HEADER_INCLUDED_B30D3A64 */
#ifndef USER_DATA_H_HEADER_INCLUDED_B30D4FBB
#define USER_DATA_H_HEADER_INCLUDED_B30D4FBB
//##ModelId=4CF281890096
class User data
{
public:
//##ModelId=4CF2AC3900EA
check();
//##ModelId=4CF2AE2A03A9
store_data();
save();
private:
//##ModelId=4CF2AC5101E4
login_id;
//##ModelId=4CF2AC6502FD
password;
//##ModelId=4CF2AE4E003E
user_name;
//##ModelId=4CF2AE56003E
email_id;
};
#endif /* USER_DATA_H_HEADER_INCLUDED_B30D4FBB */
#ifndef USER_DATABASE_H_HEADER_INCLUDED_B30D6E99
#define USER_DATABASE_H_HEADER_INCLUDED_B30D6E99
//##ModelId=4CF281380104
class User database
{
public:
//##ModelId=4CF2AAA701C5
check();
};
#endif /* USER_DATABASE_H_HEADER_INCLUDED_B30D6E99 */
#ifndef USER_REGISTRATION_FORM_H_HEADER_INCLUDED_B30D30EF
#define USER_REGISTRATION_FORM_H_HEADER_INCLUDED_B30D30EF
//##ModelId=4CF2807D0152
class User registration form
{
public:
//##ModelId=4CF2AE080271
select();
//##ModelId=4CF2AE14008C
put_data();
};
#endif /* USER_REGISTRATION_FORM_H_HEADER_INCLUDED_B30D30EF */
#ifndef VALIDATION_H_HEADER_INCLUDED_B30D1A09
#define VALIDATION_H_HEADER_INCLUDED_B30D1A09
//##ModelId=4CF2806902D8
class Validation
{
public:
//##ModelId=4CF2AC2B008C
validate_data();
//##ModelId=4CF2AE6A02AF
check_data();
};
#endif /* VALIDATION_H_HEADER_INCLUDED_B30D1A09 */

BIJIT

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BIJIT

Transféré par

Droits d'auteur :

Formats disponibles

PROBLEM STATEMENT

BVICAM’s International Journal of Information Technology (BIJIT) publishes research papers

User Register as author or

Internal Feedback Change password

Send Revise Manuscript

Project Name : BIJIT

Use case ID : BIJIT_001

Use case Name : User Registration

Brief Description : This is a use case for registration of a user.

Primary Actors : Users

Secondary Actors : None

Pre conditions: None

1. Select user registration option.

2. System will display user registration form.

3. User will enter username.

4. System will check the validity.

5. If valid enter email id and password else goto step 3

6. System will check email id and password

9. System will store data

10. System will generate confirmation mail and notification mail

11. System will send confirmation mail to user

12. System will send notification mail to BEB.

Post Conditions : 1. User should receive the confirmation mail.

Alternative Flow : None

Enter specific user

select submit store

Project Name : BIJIT

Use case ID : BIJIT_002

Use case Name : Login

Brief Description : This is a use case for logging in of a user.

Primary Actors : BEB & Users

Secondary Actors : None

1. Authors, reviewers and subscribers should be registered users of BIJIT.

1. User will enter username and password.

2. System will check the validity.

2.1 If it is valid , it will display the user type.

2.2 If it is not valid go to step 1.

Alternative Flow : None

Enter user name Check Validity

Display user type

Project Name : BIJIT

Use case ID : BIJIT_003

Use case Name : Submit Manuscript

Primary Actors : Author and System

Secondary Actors : None

1. User should login as Author

1. Select submit manuscript option.

Post Conditions : 1. BEB should receive the manuscript.

2. Author and BEB should receive the notification mail.

Alternative Flow : None

Select submit Display a blank wordpad file

click submit display message

send the manuscript

Project Name : BIJIT

Use case ID : BIJIT_004

Use case Name : Assign IR

Brief Description : This is a use case for assigning internal reviewer

Primary Actors : BEB & Internal reviewer

Secondary Actors : None

1. System checks the research area of manuscript.

Alternative Flow : None

Checks the research

Finds internal reviewers with same research Allocates an internal reviewer