SyRAP - RESEARCH AND PUBLICATION MANAGEMENT SYSTEM

SOFTWARE REQUIREMENT SPECIFICATIONS

SEMESTER	: JULY 2012 – JANUARY 2013
COURSE NAME	: SOFTWARE ENGINEERING (CSC565)
LECTURER	: AZLAN ISMAIL (PhD) (azlanismail@tmsk.uitm.edu.my)
SYSTEM NAME	: SyRAP - SYSTEM RESEARCH AND PUBLICATION MS
PROGRAM NAME	: BACHELOR OF COMPUTER SCIENCES (CS230)
CONTACT PERSON	: MOHAMMED HAIRE – 0193895882 – hairekahfi@gmail.com

STUDENT ID	STUDENT NAME	GROUP	ROLE
2011188881	MOHAMMED HAIRE BIN KAHFI	CS2303A	DEVELOPER 1
2012700441	NURUL SHIDA BINTI BAHARUDIN	CS2303A	DEVELOPER 2
2012121445	NOR'AQILAH BINTI ZULHISHAM	CS2303A	DEVELOPER 3
2012141709	AINNUR SYAHIRAH BINTI HAMZAH	CS2303A	DEVELOPER 4
2010265578	NUR ILYANA AWANIS BT ABDUL AZIZ	CS2303A	DEVELOPER 5

1.1 Background Study

1.1.1 What kind of system?

This system is about Research and Publication information that allow the user to easily store, update, delete or search for any information regarding the Research and Publication belonging to the lecturer. The system is develop for the internet base so it can easily access it through the world wide web.

1.1.2 Who needs the system

Management Staff need the system so they can observe any current registration for each new Research or Publication from the lecturer. They have their own report so they can monitor every lecturer progress through the years. For the lecturer, they could use this system to store their Research and Publication material in one safe reliable place. Hence they also can search any releven information about other lecturers material. Admin staff responsible to store and manage data user of this system, print statistic and report of the research and publication.

1.1.3 Why they need the system

They need this system to easy their task or work such as material for their lesson in class, their own research or maybe for another use. Secondly, they can observe any updates in this system and they have their own report so they can improve or change anything in this system.Thirdly, responsible to store and manage data user of this system, print statistic and report of the research and publication

1.1.4 How the proposed system can improve their activities

Speed up their movement because the user of this system just do the research by sitting on the chair and search using this system

The user no need to go to library or galleries or museum to search for information because this system provide a lot of research and publication. At the same time, they save their petrol, money and energy.

1.1.4 An existing or similar system developed for other organizations

An example for the existing system is the UiTM PTAR Library, such as WebinfoLine and E-Book . Students can easily access to the system and search for book based on the series number or title of the books.

1.2 Development Methodology (Software Process Model)

Development Methodology (Software Process Model)

Inception Phase:
During the inception phase the core idea is developed into a product vision. In this phase, we review, discuss, and understand the business case of the project. The inception phase establishes the product feasibility and delimits the project scope.

Elaboration Phase:
During the elaboration phase the majority of the Use Cases are specified in detail and the system architecture is designed. This phase focuses on the "Do-Ability" of the project. We identify significant risks and prepare a schedule, staff and cost profile for the entire project.

Construction Phase:
During the construction phase the product is moved from the architectural baseline to a system complete enough to transition to the user community. The architectural baseline grows to become the completed system as the design is refined into code.

Transition Phase:
In the transition phase the goal is to ensure that the requirements have been met to the satisfaction of the stakeholders. This phase is often initiated with a beta release of the application. Other activities include site preparation, manual completion, and defect identification and correction. The transition phase ends with a postmortem devoted to learning and recording lessons for future cycles.

1.3 Project Milestones and Deliverables

Project Milestones and Deliverables

No	Items	File Naming	Deadline
1.	Project Proposal	Proposal_SyRAP.mp4	Week 3 Monday, 12pm 11/3/13 – 18/3/13
2.	Software Requirements Specification · Generating General Use Case · Generating Details Use Case · Generating SRS Report – Draft Version		13/3/13 – 02/4/13
3.	Submit SRS Report Draft Version to Lecturer		Week 6 Monday, 12pm 08/4 /13
4.	Prototype Development · Creating Table · Creating Component · Creating Interface · Creating Component		09/4/13 – 20/5/13
5.	Generating Finalized SRS Report		Week 8 Monday, 12pm 09/4/13 – 28/4/13
6.	Submit SRS Report Final Version to Lecturer		29/4 /13
7.	Software Design Document		30/4/13 – 20/5/13
8.	Software Testing Requirement · Verification · Validation		20/5/13 – 10/6/13
9.	Submit SDD and STR Report Final to Lecturer		Week 13 Monday, 12pm 10/6/13

1.4.1 Task breakdown & Job assignments

Task breakdown & Job assignments

1.4.2 Gantt Chart

2.1 Overall UseCase Diagram

This diagram shows process involve there main user (actors) ADMIN STAFF and , MANAGEMENT STAFF and LECTURER. Lecturer as the main user can access the system to Register , Update or Delete information about their own Research and Publication material. Admin Staff is responsible to manage the lecturer information and also handling the reports for the management. Management Staff had the right to view all registered information and also access the management report through online access.

Actor (s) :

ADMIN STAFF - Admin Staff is the administration staff in the Faculty administration office which will handle all he registration of the lecturer who will involve in the system. They also will handle the reports for the management.

LECTURER - Academic Staff in the Faculty is the main user who will use the system to register information about Research and Publication. They also can search from the system for any update of information among the lecturer.

MANGEMENT STAFF - The upper level of administrator staff such as the Vice Canselor, Dean or the Head of department. The will using the system to get reliable data from the report and statistic provided from the system to make and organization decision .