Scribd
Upload
34 views23 pages

Project Document Template

The document outlines the formatting requirements and structure for a research study. It specifies the paper size, margins, spacing, pagination, and provides an example title page. It also lists the main sections that should be included which are an introduction, system requirements specification, Scrum process, conclusion, references, and appendices.

Uploaded by

sumayangiresh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
34 views23 pages

Project Document Template

The document outlines the formatting requirements and structure for a research study. It specifies the paper size, margins, spacing, pagination, and provides an example title page. It also lists the main sections that should be included which are an introduction, system requirements specification, Scrum process, conclusion, references, and appendices.

Uploaded by

sumayangiresh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 23

REQUIREMENTS/FORMAT SETTINGS

PAPER
Use white letter size paper (8 ½ x 11 in). Orientation should be portrait style.

LANGUAGE
The official language to be used in writing a research study is American English.
All sentences must be complete with acceptable grammar and correct spelling.

MARGINS
Left
Margin: 1.5”
Right Margin: 1”
Top Margin: 1”
Bottom Margin: 1”

SPACING
Use a five-space indention (or press Tab in the keyboard) every paragraph. The body of the study
should be typed in double spaces.

PAGINATION
Pages should be numbered consecutively in the top right throughout the study.
Page 1 begins in the first page of the chapter. Page numbers are not to be enclosed in
parentheses, hyphens or other decorative devices. Preliminary pages preceding the first chapter
are numbered using small Roman numerals (I, ii, iii, etc.). The title page should not be
numbered.

Example of Title Page below:


Republic of the Philippines
Cavite State University
Don Severino delas Alas Campus
Indang, Cavite
1
2
COLLEGE OF ENGINEERING AND INFORMATION TECHNOLOGY
1
DEPARTMENT OF INFORMATION TECHNOLOGY
1
2
3
In Partial Fulfillment of
COSC 75A: Software Engineering II
1
2
3
A Proposal of
1
Title of the Software Project
1
2
3
Submitted to:
1
Mr. Stephen Andrei O. Rocillo
Instructor
1
2
3
Submitted by:
1
Student Name

Date submitted:
1
Month date, year
Table of Contents

Page
INTRODUCTION 2
Background 3
… …
SYSTEM REQUIREMENTS SPECIFICATIONS 4
Introduction 5
… …
1

INTRODUCTION
1.1 Background

1.2 Statement of the Problem

1.2.1 Main Problem

1.2.2 Specific Problem (cite fishbone diagram)

1.3 Objectives

1.3.1 General Objectives

1.3.2 Specific Objectives

1.4 Discussion of Existing and Proposed System

1.4.1 Existing System (cite DFD)

1.4.2 Proposed System (cite DFD)

1.5 Scope and Limitations


1

SYSTEM REQUIREMENTS SPECIFICATION


2.1 Introduction
2.1.1 Purpose
2.1.2 Scope
2.1.3 Overview
2.2 Overall Description
2.2.1 Product Perspective
2.2.2 Product Features/Functions
2.2.3 User Classes and Characteristics
2.2.4 Assumption and Dependencies
2.3 Specific Requirements
2.3.1
2.3.1.1
2.3.1.2
2.3.1.3
2.4 External Interface Requirements
2.4.1
2.5 Other Non-Functional Requirements
2.5.1
2.5.2
2.5.3
2.5.4
1

SCRUM PROCESS
3.1 Overview
3.2 Project Organization
3.2.1 Scrum Roles (and Responsibilities)
3.2.1.1 The Scrum Master
3.2.1.2 The Product Owner
3.2.1.3 The Members
3.3 Work Plan
3.3.1 Schedule allocation (cite Gantt chart)
3.4 Project Deliverables (milestones)
3.4.1 Scrum Flow (discuss)
Figure 3.4.1 (Scrum Model)
3.4.2 Product Backlog (discuss, cite product backlog)
3.4.3 Sprint Backlog (discuss the process and result, cite sprint backlogs and burn down chart)
3.5 Quality Control (discuss results base on the no. of sprints)
3.5.1 Unit Testing (cite unit testing test cases)
3.5.2 System Testing (cite system testing test cases)
3.6 Lessons Learned (individual members of the group)
1

CONCLUSION
1

REFERENCES
(sources)
1

APPENDICES
1

10

Appendix A

Figures
(fishbone, dfd, burndown chart)
1

10

Appendix B

Tables
(gantt, product backlog, sprint backlog)
1

10

Appendix C

Test Cases
((unit testing, system testing )testing in each sprint)
1

10

Appendix D

Screenshots

You might also like