FACULTY OF INFORMATION MANAGEMENT

UNIVERSITI TEKNOLOGI MARA

GROUP PROJECT GUIDELINES

FINAL PROJECT ( 20% )

1.0 IMS 552 INFORMATION SYSTEMS MANAGEMENT

All group members will usually receive the same grade. If a group member is
not pulling his or her weight, it reflects badly on everyone. If this situation
cannot be worked out among yourselves, be sure to discuss it with the
lecturer/supervisor concerned.
Project Grading

Upon completion of the project, students will receive an overall project grade.
It is important to note that this grade reflects not only the final products of the
project (results, report, etc), but also the process by which they were attained.
No last-minute effort will turn a mediocre project effort into an A!
Papers you submit, should be well organized, thoughtful, proof-read and
The Project Report spell-checked!

The project report is an extremely important aspect of the project. It serves to show
what you have achieved and try to ensure that it contains the following elements: -

: Introduction of project

: Organization background

: Corporate vision, mission, objective, goal

: Organization structure chart

: Functional description of departments/divisions/units

: Role and function of departments/divisions/units

: Data used in the organization

 : List of Information systems

: Brief explanation, function and objective of each IS

: Types of IS

Details of Selected IS

: Information system background

: Functional description of IS

: IS components

: IS activities

: Hardware and software configuration

: Information System problem

Performance of IS

: Strength and weaknesses of IS

: Opportunities and threats of IS

: Generate and evaluate alternatives

: Recommendation and action plan

: Conclusion

Don't make the mistake of leaving the write-up to the last minute. Ideally you should
produce the bulk of the report as you go along and use the last week or two to bring
it together into a coherent document.

The physical layout and formatting of the report is also important, and yet is very
often neglected. A tidy, well laid out and consistently formatted document makes for
easier reading and is suggestive of a careful and professional attitude towards its
preparation.

Remember that quantity does not automatically guarantee quality. Conciseness,

clarity and elegance are invaluable qualities in report writing, just as they are in
programming, and will be rewarded appropriately.
: Title page This should include the University, faculty and program’s name,
project title and the name of the author of the report, group members,
course code, date etc. You can also list the name of your lecturer if you
wish.
: Abstract The abstract is a very brief summary of the report's contents. It
should be about half a page long. Somebody unfamiliar with your project
should have a good idea of what it's about, having read the abstract alone
and will know whether it will be of interest or not.
: Acknowledgements It is usual to thank those individuals who have
provided particularly useful advice, assistance, technical or otherwise,
during your project.
: Contents page This should list the main chapters and (sub)sections of your
report. Choose self-explanatory chapter and section titles and use double
spacing for clarity. If possible you should include page numbers indicating
where each chapter/section begins. Try to avoid too many levels of
subheading - three is sufficient.
: Introduction This is one of the most important components of the report. It
should begin with a clear statement of what the project is about so that the
nature and scope of the project can be understood by a lay reader. It should
summarize everything you set out to achieve and provide a clear summary
of the project's background and relevancy.
The introduction should set the scene for the project and should provide the
reader with a summary of the key things to look out for in the remainder of
the report. It is sometimes useful to state the main objectives of the project
as part of the introduction.
: Background The background section can be included as part of the
introduction but is usually better as a separate chapter.
: Avoid plagiarism: if you take another person's work as your own and do
not cite your sources of information/inspiration you are being dishonest; in
other words you are cheating. When referring to other pieces of work, cite
the sources where they are referred to or used, rather than just listing them
at the end.
: Evaluation Be warned that many projects fall down through poor
evaluation. It is extremely important that you evaluate what you have done
both in absolute terms and in comparison with existing techniques,
software, hardware etc. This might involve quantitative evaluation, for
example based on numerical results, performance etc. or something more
 qualitative such as expressibility, functionality, ease-of-use etc. At some
point you should also evaluate the strengths and weaknesses of what you
have done.
: Conclusions The project's conclusions should list the things which have
been learnt as a result of the work you have done.
: References: This consists of a list of all the books, articles, manuals etc.
used in the project and referred to in the report. You should provide enough
information to allow the reader to find the source. A weakness of many
reports is inadequate citation of a source of information. Each entry should
list the author(s) and title of the piece of work and should give full details of
where it can be found.
: Appendix The appendices contain information which is peripheral to the
main body of the report. Information typically included are things like parts
of the code, tables, proofs, test cases, brochures or any other material
which would break up the theme of the text if it appeared in situ. Photos
also add a lot to the story you are telling. You should try to bind all your
material in a single volume if possible.

Submission of Report 13 Jun 2015

Puan Hasnah Hashim

Prepared By
[email protected]