1. Goal, Objectives, Scopes, Problem Background / Problem Statement and The Importance of SW Development / Research Project

2. Goal
The ultimate/absolute purpose of your s/w development / research project.
1 sw development / research project : aims for 1 goal
Must be achieved/presented/reported at the end of your project .
Written in a clear, concise form (write one or a combination of simple sentences).
In a single short paragraph

3. Objective(s)
List of things need to be achieved, lead to the accomplishment of project goal.
Within your control
Your responsibility
Measurable
Time based

4. Objectives the SMART acronym reminds you that objectives must be:
Specific – An Objective can't be vague – be specific
Measurable - Define a method of measuring the objective so you know when it is achieved (phew!)
Agreed-To/Achievable - you and your supervisor need to agree to the objective, and it also must be do-able
Realistic/Rewarding - It must be a realistic objective, and it must make sense to do it
Time-related - without a schedule and due date, it will just keep going, and going, and going...

5. so … All your Objectives should have clear titles e.g.
“Research current hotel management systems systems that attempt database integration”
Objectives should all have deliverables, i.e. they can be measured – (how far have I got?)
you will know when the objective is achieved because you will have the deliverable ready
Objectives should be agreed with your supervisor
(but you will do all the work )
Objectives should all contribute directly to your project and getting a good grade
Objectives should all have a time schedule

6. split things up
Anything complicated benefits from being split into smaller pieces; (divide and conquer).
Your Research objective could split into
background ideas, requirements analysis, problems, technology review, data gathering (e.g. on similar products, applications, sites) …
Your Build objective could split into
Gathering functional/non functional requirements, UML diagrams, Design artifacts, implementation issues …
Your Evaluate objective could split into
testing, performance, reliability, usability, security …

7. make sure that You choose sensible objectives
use verbs like: to investigate, to study, to develop, to analyse and so on
 “One objective is to read that ASP.Net book”.
Each objective or task must
Have a set of known activities (e.g. using electronic databases, creating UML or code, testing …)
Have a set of deliverables (e.g. the background section of the introduction chapter, a set of Use Case, a Class Diagram …)
Once you have defined an objective, estimate how long it will take you to achieve it (i.e. have all the deliverables)
Add all your timescales together into your Project Schedule.

8. Objective – (how many?) No exact number.
General guideline: min 2 to max 5
Having only 1 objective is too general, similar to project goal.
Over than 5 is too much/detail (know your ability/ time constrain etc…).
Ideally +-3
Should be written as a point form
last but not least, it depends on discussion & agreement with s/visor

9. Scope(s)
the  list of assumptions, limitations and constraints that you put in your project.
As a boundary – of what you responsible for/not.
Is important in determining the project can be conducted successfully / not.
Eg: if the project involves/requires data gathering , from organizations or case studies,  put a scope so that it wont be too big/difficult to be accomplished (impede you to move on).

10. Scope – how to write
The use of specific software/hardware/simulator/prototype in your project.
Study to gather info/reqs from only specific location/company.
Written in point form

11. Problem Background
General description of the problem /existing system/current implementation/how people doing the work, being studied.
For project involves the organization, or project which aims to enhance/improve the current system /way of people doing their work (manually).

12. Problem Statement
Statement of what are the actual problem to be solved in your project.
Not necessarily expressed in all projects.
Usually for a research-based projects.
Best written as a question, followed by other supporting questions.

13. Importance of the project
What is the motivation or incitement
Explain the reasons and justification of your project.
Why is it important?
The advantages
Benefits to be gained
Describe the parties (1,2,3,4) to benefit and how benefits are obtained.

14. Kepentingan Buku log Buku log akan dinilai
Perjumpaan perlu dilakukan sekurang kurangnya sekali dalam 2 minggu
Merekodkan setiap perjumpaan formal yang melibatkan lapuran terhadap kerja yang telah dilakukan dan kerja yang seterusnya perlu dilakukan
10% markah diberikan kepada perjumpaan yang aktif sepanjang semester.

15. Kandungan Buku Log
3 daripada 4 tahap kemajuan projek/kajian perlu disiapkan dalam PSM 1 iaitu:
Kajian
Analisa
Rekabentuk
Pencapaian minggu ini adalah lapuran pelajar terhadap kerja-kerja yang telah disiapkan semenjak lapuran yang terdahulu sehingga kini
Cadangan pencapaian minggu hadapan adalah hasil perbincangan dengan penyelia untuk kerja-kerja seterusnya yang perlu dan akan dilaksanakan

16. Project Schedule (Gantt Chart)
A good proposal will include a schedule showing how all the individual objectives fit together and timescales add up
A Gantt chart is a good way to do this (use Microsoft Project)
If the total time is too long then you need to reduce the scope (how much you will do) of some of the time-consuming objectives

17. Carta Gantt Mark milestones (milestones) for each major activity
(activity vs date)
Example:
Project goal, objectives and scopes finalized/confirmed
Major research materials and literature has been obtained
All major user requirements has been gathered, conflict resolved, documented (SRS).
Completion of System Preliminary Design and documented (SDD)
Presentation materials/slides has been prepared
Completion of Chapter 01, 02 … n of your PSM report.