CC304 Business Case Project

Lecturer: Mr. Rabin Thapa

Student Name: Aakash Maharjan Student ID: 1001849291

Student Name: Bhusan Pudasaini Student ID: 1001749171
Student Name: Nhyu Joshi Student ID: 1001749072
Student Name: Rohit Adhikari Student ID: 1001749217

WEEKLY GROUP PROGRESS REPORT- Week 1

PRESENT:
Aakash Maharjan
Bhusan Pudasaini
Nhyu Joshi
Rohit Adhikari

ABSENT:

OBJECTIVE: (in point form)

 Search for related journals and similar websites

 Work division of team Members for researching
 Understand the Project Requirements

ACTION TO BE TAKEN:(in point form)

 Hold a team meeting for discussion about project

 Divide the researching materials between team members

MATTER ARISE: (in point form)

 Confusion in project requirements

 Hard to find related journals
 Confusion in research materials

ssss

SIGNATURE: ________________________
WEEKLY GROUP PROGRESS REPORT- Week 2

PRESENT:
Aakash Maharjan
Bhusan Pudasaini
Nhyu Joshi
Rohit Adhikari

ABSENT:

OBJECTIVE: (in point form)

 Research on the features of similar websites

 Creating mind map
 Understanding features to include in our system

ACTION TO BE TAKEN:(in point form)

 Hold a discussion session with team members to discuss about the key features
for our system
 Create mind map accordingly
 Divide the websites to research between team members

MATTER ARISE: (in point form)

 Confusion in deciding the key features for the system

 Confusion in features of existing systems

SIGNATURE: ________________________
WEEKLY GROUP PROGRESS REPORT- Week 3

PRESENT:
Aakash Maharjan
Bhusan Pudasaini
Nhyu Joshi
Rohit Adhikari

ABSENT:

OBJECTIVE: (in point form)

 Become familiar with SRS document format

 Become familiar with UML diagrams
 Work division of SRS document
 Choosing tool for making UML Diagrams

ACTION TO BE TAKEN:(in point form)

 Hold a team discussion session to get familiar with SRS document and UML
diagrams
 Divide work between team members
 Choose a tool to make UML diagram

MATTER ARISE: (in point form)

 Confusion in SRS Document

 Confusion in understanding UML Diagrams
 Members confused about how to use diagram tools

SIGNATURE: ________________________
WEEKLY GROUP PROGRESS REPORT- Week 4

PRESENT:
Aakash Maharjan
Bhusan Pudasaini
Nhyu Joshi
Rohit Adhikari

ABSENT:

OBJECTIVE: (in point form)

 Start SRS Document

 Start making UML diagrams

ACTION TO BE TAKEN:(in point form)

 Hold a team discussion session to discuss about various topics of SRS documents
and how to create UML diagrams according to our system
 Start making SRS document and diagrams according to divided task.

MATTER ARISE: (in point form)

 Confusion of members on writing SRS document

 Confusion of team members on creating diagrams according to the system

SIGNATURE: ________________________
WEEKLY GROUP PROGRESS REPORT- Week 5

PRESENT:
Aakash Maharjan
Bhusan Pudasaini
Nhyu Joshi
Rohit Adhikari

ABSENT:

OBJECTIVE: (in point form)

 Finish first draft of SRS document

 Finish first draft of diagrams

ACTION TO BE TAKEN:(in point form)

 Compile the SRS document and diagrams

 Send compiled SRS to supervisor for review

MATTER ARISE: (in point form)

 Mistakes in diagrams and SRS document

 Diagrams missing in SRS document

SIGNATURE: ________________________
WEEKLY GROUP PROGRESS REPORT- Week 6

PRESENT:
Aakash Maharjan
Bhusan Pudasaini
Nhyu Joshi
Rohit Adhikari

ABSENT:

OBJECTIVE: (in point form)

 Division of work according to new diagrams and topics

 Finalize SRS document
 Finalize Diagrams
 Compile SRS document and diagrams

ACTION TO BE TAKEN:(in point form)

 Divide new topics between team members

 Finalize SRS document and diagrams
 Upload finalized SRS document and diagram

MATTER ARISE: (in point form)

 Confusion in new required diagrams

SIGNATURE: ________________________