Chapter 1 Introduction: Project Overview

Chapter 1 Introduction
Project overview
This chapter is concerned with similar concerns to the abstract and should provide an
overview of the project with more detail. It sets the scene by describing the general area
that the project work addresses and also identifies the need for the specific work that the
student has carried out.
1.2. Background of problem

This chapter should describe brief description of the existing problems as a justification
to conduct the project/survey.
1.3 Project objective

This section focus on why you choose this project and how it can benefit the user
such as:
1. To study …
2. To analyze and design …
3. To develop …
1.4. Scope
This should define the boundary of the project in terms of
1. The core functionality system

2. Data
3. Software/Hardware/Platform
4. Features
5. User
6. Type of testing
1.5. Importance of project

This chapter should describe on:
 Potential benefits to the organization; or
 New contribution to the field of study
1.6. Gantt Chart
A Gantt chart outlines what aspects of the project will be completed by when. The Gantt
chart must show the duration taken for selecting group members until delivering the final
report. You can refer to the sample report to see what Gantt chart looks like. You can
create Gantt chart in Microsoft Excel, MS Project or other project management software.
Chapter 2 Literature Review
This chapter is concerned with presenting a survey of background relevant to the area of investigation,
leading to an evaluation of pre-existing implementations or designs and of candidate re-usable
components. The selection of what to review should be guided by a clear understanding of the aims and
requirements of the project. The source for the background is published material, in general, journal and
conference papers, theses, research monographs, textbooks, web sites and product information.
Remember to acknowledge all work that is quoted.
2.(n-2) Chapter
This chapter should concern with various literatures related to the topic chosen.
• It could be an extension of a certain research/study/project; or
• Other studies such as similar applications, techniques existing in the current
market, models, similar business process, features of similar system, similar
studies, system development strategies on similar projects
All sources used should be cited in the text; if any words are copied directly then they
should be placed between quotes and the source acknowledged.
2.(n-1) Chapter
This chapter should conclude what has been done in the investigation with he/she own
analytical analysis of the reviews, as part of the justification for nay method that he/she
would choose later, or as a direct benefit to continue their project; or on how the review
helps the project.
Chapter 3 Methodology
This chapter focuses on the research methodology used for the project, which are the project methodology
or software development methodology.
3.1 Project Methodology

• This chapter should describe brief description of the methodology used for
the project.
3.2 System development methodology

This chapter should describe brief description of the methodology used for the software
development, such as:
• Structured System Analysis & Design Methodology (SADM)
• Object Oriented Methodology
Chapter 4 Findings
This chapter is concerned with the analysis of the problem that the project addresses, and initial design of
the system/artifact (or of the investigation if the project is of an experimental type) and justifying how it
will meet the identified requirements.
 How the analysis and design have been carried out - the approach(es) and
notation(s) used etc;
 The analysis of the requirements for the deliverable.
 The conceptual level design;
As appropriate, alternatives considered may be discussed, with justification for the approach taken. The
analysis and / or design should be expressed and detailed in a suitable form.
4.1. Organizational analysis

This chapter should describe the organizational analysis in terms of:
• Structure
• Functions
• Core business
• Existing IS/IT systems
• Problem statement in the organizational context
4.2. Current Business Process and Data Model

This chapter should describe a thoroughly original analysis of the business process,
either:
Current Framework
Structured System Analysis & Design Methodology (SADM)
• Context Diagram
• Data-Flow Diagram (DFD)
• Entity-Relational Diagram (ERD)
• Data Dictionary
This should include the analysis of the current situation stated the weaknesses of the
current system.
4.3. User Requirements

This chapter should list the functional breakdown of the system.
4.4. To-Be Process and Data Model

This chapter should describe a thoroughly original design of:
• Proposed Framework
• Business process (To-be process), either
Structured System Analysis & Design Methodology (SADM)
• Context Diagram
• Data-Flow Diagram (DFD)
• Entity-Relational Diagram (ERD)
• Data Dictionary
• Physical Design/System Architecture
This chapter also should describe a thoroughly original design of the conceptual design
(System Architecture). This also should include the expected competitive advantage gain
from the purposed system
Chapter 5 Design Implementation and Testing
This chapter is concerned with the design of the implementation, and test of the designed system.
 The result of the design;
 The deliverable;
 User manual for the administrator.
As appropriate, alternatives considered may be discussed, with justification for the approach taken. The
analysis and / or design should be expressed and detailed in a suitable form.
5.1. Coding Approach

This chapter should describe the coding approach in terms of:
• Code Structure
• Snapshot of your Critical Programming Codes
5.2. Test Result / System Evaluation

This chapter should list the test result or system evaluation in terms of:
• Usability
• Functionality
• Test Result
• User Acceptance Test
5.3. User Manual for Administrator

This chapter should provide the user manual for administrator in terms of:
• Hardware configuration or setup
• System Integration Manual
• Installation Procedure
Chapter 6 Discussion & Conclusion

This chapter discuss on the achievement, constraints, challenges and aspirations when conduct the
project.
6.1. Summary of all chapters
6.2. Achievements
This chapter should discuss the achievement in the findings.
6.3. Constraints & Challenges

This chapter should list the constraints and challenges when conduct the project.
6.4. Aspirations
This chapter should list the expectation achievement at the end of Final Project.
6.5. Conclusions
This chapter should re-outline the achievement, constraints, challenges and aspirations
when conduct the project.

Chapter 1 Introduction: Project Overview

Uploaded by

Copyright:

Available Formats

Chapter 1 Introduction: Project Overview

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 1 Introduction: Project Overview

Uploaded by

Copyright:

Available Formats

Chapter 1 Introduction

1.2. Background of problem

1.3 Project objective

1. The core functionality system

1.5. Importance of project

1.6. Gantt Chart

3.1 Project Methodology

3.2 System development methodology

4.1. Organizational analysis

4.2. Current Business Process and Data Model

4.3. User Requirements

4.4. To-Be Process and Data Model

5.1. Coding Approach

5.2. Test Result / System Evaluation

5.3. User Manual for Administrator

Chapter 6 Discussion & Conclusion

6.1. Summary of all chapters

6.3. Constraints & Challenges

You might also like